[riot-notifications] [RIOT-OS/RIOT] Gnrc sixlowpan frag/enh/expose interval type (#10988)
notifications at github.com
Mon Feb 11 15:21:41 CET 2019
The RIOT community cares a lot about code quality.
Therefore, before describing what your contribution is about, we would like
you to make sure that your modifications are compliant with the RIOT
coding conventions, see https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions.
### Contribution description
For the [VRB] I also need to track which the intervals of the fragments already received (mostly for finding out when I am able to get rid of a VRB entry, see [this conversation][VRB entry removal]). I also incorporated the frame interval list in the public reassembly buffer entry fields, since parts of those will be used for the VRB entry type.
[VRB entry removal]: https://mailarchive.ietf.org/arch/msg/6lo/bTm2REo4PpVcMFH04mF_SlPvS_M
### Testing procedure
Sending and receiving fragmented packets with `gnrc_networking` should still work. `tests/gnrc_sixlowpan_frag` should still compile and pass.
Details steps to test your contribution:
- which test/example to compile for which board and is there a 'test' command
- how to know that it was not working/available in master
- the expected success test output
### Issues/PRs references
None so far.
Examples: Fixes #1234. See also #5678. Depends on PR #9876.
Please use keywords (e.g., fixes, resolve) with the links to the issues you
resolved, this way they will be automatically closed when your pull request
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
You can view, comment on, or merge this pull request online at:
-- Commit Summary --
* gnrc_sixlowpan_frag: expose fragment interval type
* gnrc_sixlowpan_frag: add intervals to public type
-- File Changes --
M sys/include/net/gnrc/sixlowpan/frag.h (20)
M sys/net/gnrc/network_layer/sixlowpan/frag/rbuf.c (32)
M sys/net/gnrc/network_layer/sixlowpan/frag/rbuf.h (19)
M tests/gnrc_sixlowpan_frag/main.c (8)
-- Patch Links --
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications