net: coap: Fixed discovery response formatting according to RFC6690 #31610
Conversation
This file contains 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
kasunch
force-pushed
the
rfc6690_fix
branch
2 times, most recently
from
ca0a0ee to
a688863
Compare
kasunch
changed the title
rlubos
reviewed
Jan 26, 2021
jukkar
reviewed
Jan 26, 2021
|
Please, no merge commits in PRs. Just rebase your stuff against latest master and force push to this PR. |
|
I will rebase and push. |
CoAP RFC (RFC7252) states that end points should support the CoRE Link Format of discoverable resources as described in RFC6690 (refer section 7.2 of the RFC7252). Fixes zephyrproject-rtos#31609 Signed-off-by: Kasun Hewage <[email protected]>
rlubos
approved these changes
Jan 27, 2021
|
Lookd like only the build 14 was failed. Any idea? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR resolves #31609
Signed-off-by: Kasun Hewage [email protected]