gnrc_pktbuf: allow write-protect of size 0 snips#11161
Merged
2 commits merged intoRIOT-OS:masterfrom Mar 15, 2019
Merged
Conversation
Size 0 snips are legal packet snips (empty payload e.g.) so it doesn't make sense to issue an error in the write-protection in that case. API documentation doesn't mention it either and the tests still pass with the check removed.
Size 0 snips are legal packet snips (empty payload e.g.) so it doesn't make sense to issue an error in the write-protection in that case. API documentation doesn't mention it either and the tests still pass with the check removed.
This was referenced Mar 12, 2019
|
With txtsnd from EDIT: zero bytes of payload of course :) |
ghost
approved these changes
Mar 15, 2019
This pull request was closed.
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
Size 0 snips are legal packet snips (empty payload e.g.) so it doesn't
make sense to issue an error in the write-protection in that case.
API documentation doesn't mention it either and the tests still pass
with the check removed.
Testing procedure
Unittests should still pass, both with normal configuration
make -C tests/unittests tests-pktbuf testand
USEMODULE=gnrc_pktbuf_malloc make -C tests/unittests tests-pktbuf test(just noticed that this test fails in master as well due to an unrelated problem -.-)
Issues/PRs references
Requires #11163 to be fixed to actually be able to send empty packets with
gnrc_networking.