Fixes for Zephyr secure sockets integration#10583
Open
Frauschi wants to merge 1 commit into
Open
Conversation
|
Contributor
Author
|
Jenkins retest this please |
ColtonWilley
reviewed
Jun 4, 2026
| # General config | ||
| CONFIG_NEWLIB_LIBC=y | ||
|
|
||
| # Pthreads |
Contributor
There was a problem hiding this comment.
This is not for using Zephyr native TLS interface swap, this is for general app integration. Im not sure if we should be changing these defaults unless we are absolutely sure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up for #10268 with some more changes required for the updated patch set for Zephyr 4.3 secure sockets integration (for wolfSSL/osp#330 with an iteration of the patch currently under review by @ColtonWilley).