Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gnrc_sixlowpan_frag: remove redundant PID member #11015

Merged
merged 2 commits into from Feb 15, 2019

Conversation

miri64
Copy link
Member

@miri64 miri64 commented Feb 14, 2019

Contribution description

The interface ID is actually also provided in pkt so providing it in the gnrc_sixlowpan_msg_frag_t struct is redundant.

Testing procedure

examples/gnrc_networking on a 6Lo-compatible board (e.g. iotlab-m3, samr21-xpro, etc.) should still be able to ping with large payloads (e.g. >100) to a node flashed with examples/gnrc_border_router (link-local addresses is enough).

Issues/PRs references

None.

@miri64 miri64 added Area: network Area: Networking Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Feb 14, 2019
@miri64 miri64 added this to the Release 2019.04 milestone Feb 14, 2019
Copy link
Member

@smlng smlng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise looks good

@@ -89,10 +89,9 @@ typedef struct {
*/
typedef struct {
gnrc_pktsnip_t *pkt; /**< Pointer to the IPv6 packet to be fragmented */
size_t datagram_size; /**< Length of just the (uncompressed) IPv6 packet to be fragmented */
uint16_t datagram_size; /**< Length of just the (uncompressed) IPv6 packet to be fragmented */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unrelated, or at least a second commit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split out in its own commit.

miri64 and others added 2 commits February 15, 2019 11:23
The interface ID is actually also provided in `pkt` so providing it in
the `gnrc_sixlowpan_msg_frag_t` struct is redundant.
It can't get bigger, so it doesn't make sense to waste another 2 byte
on it.
@miri64 miri64 force-pushed the gnrc_sixlowpan_frag/enh/rm-pid branch from a261a2d to 0954fab Compare February 15, 2019 10:26
@smlng smlng added Reviewed: 1-fundamentals The fundamentals of the PR were reviewed according to the maintainer guidelines Reviewed: 2-code-design The code design of the PR was reviewed according to the maintainer guidelines Reviewed: 4-code-style The adherence to coding conventions by the PR were reviewed according to the maintainer guidelines Reviewed: 5-documentation The documentation details of the PR were reviewed according to the maintainer guidelines labels Feb 15, 2019
@miri64
Copy link
Member Author

miri64 commented Feb 15, 2019

Murdock's also happy :-)

@miri64
Copy link
Member Author

miri64 commented Feb 15, 2019

Since I'm about to open a PR with another modification to gnrc_sixlowpan_msg_frag_t I merge so I can directly rebase.

@miri64 miri64 merged commit 8da4957 into RIOT-OS:master Feb 15, 2019
@miri64 miri64 deleted the gnrc_sixlowpan_frag/enh/rm-pid branch February 15, 2019 11:50
@miri64
Copy link
Member Author

miri64 commented Feb 15, 2019

Since I'm about to open a PR with another modification to gnrc_sixlowpan_msg_frag_t I merge so I can directly rebase.

(see #11021)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: network Area: Networking CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Reviewed: 1-fundamentals The fundamentals of the PR were reviewed according to the maintainer guidelines Reviewed: 2-code-design The code design of the PR was reviewed according to the maintainer guidelines Reviewed: 4-code-style The adherence to coding conventions by the PR were reviewed according to the maintainer guidelines Reviewed: 5-documentation The documentation details of the PR were reviewed according to the maintainer guidelines Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants