gnrc_pktdump: add GNRC_NETTYPE_IPV6_EXT output#10383
Merged
miri64 merged 1 commit intoRIOT-OS:masterfrom Dec 18, 2018
Merged
Conversation
2b45051 to
e06cdcd
Compare
Member
Author
|
Rebased to current master. This is a really low hanging fruit ;-). Anyone wants to review? |
Member
Author
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
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.
Contribution description
Just noticed in #10382 that
GNRC_NETTYPE_IPV6_EXTsnips are marked asNETTYPE_UNKNOWNingnrc_pktdump(but the PRs are independent).Testing procedure
Compile #10382 with and without this PR. If you set
echoin the testrunner toTrueyou will see that the marked extension headers are shown asNETTYPE_IPV6_EXTinstead ofNETTYPE_UNKNOWN(remark: extension headers shown withNETTYPE_UNDEFare unmarked and thus shown correctly in that test).Issues/PRs references
None (but #10382 required for testing)