-
Notifications
You must be signed in to change notification settings - Fork 2k
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
rpl: remove global variable indicating the root node #2625
Merged
OlegHahm
merged 1 commit into
RIOT-OS:master
from
cgundogan:rpl_remove_global_root_indication
Apr 29, 2015
Merged
rpl: remove global variable indicating the root node #2625
OlegHahm
merged 1 commit into
RIOT-OS:master
from
cgundogan:rpl_remove_global_root_indication
Apr 29, 2015
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
cgundogan
added
Type: enhancement
The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Area: network
Area: Networking
labels
Mar 17, 2015
cgundogan
force-pushed
the
rpl_remove_global_root_indication
branch
from
March 19, 2015 10:59
7170619
to
549b5d3
Compare
cgundogan
added
the
State: waiting for other PR
State: The PR requires another PR to be merged first
label
Mar 19, 2015
needs rebase |
OlegHahm
removed
the
State: waiting for other PR
State: The PR requires another PR to be merged first
label
Mar 19, 2015
cgundogan
force-pushed
the
rpl_remove_global_root_indication
branch
from
March 19, 2015 18:44
549b5d3
to
e20fbbb
Compare
rebased to current master |
uint8_t rpl_is_root(void) | ||
{ | ||
return i_am_root; | ||
for (uint8_t i = 0; i < RPL_MAX_DODAGS; i++) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to keep the code consistent it would be nice to iterate like you did for instance here
OlegHahm
force-pushed
the
master
branch
3 times, most recently
from
March 31, 2015 13:01
9f184dd
to
45554bf
Compare
addressed @BytesGalore's comment to change the style of the for-loop |
OlegHahm
added
the
CI: needs squashing
Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable
label
Apr 15, 2015
after merging #2831 my tests succeed. ACK. Please squash! |
cgundogan
force-pushed
the
rpl_remove_global_root_indication
branch
from
April 28, 2015 16:13
0395f8b
to
b557000
Compare
cgundogan
removed
the
CI: needs squashing
Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable
label
Apr 28, 2015
@OlegHahm squashed and rebased |
OlegHahm
added a commit
that referenced
this pull request
Apr 29, 2015
…tion rpl: remove global variable indicating the root node
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: network
Area: Networking
Type: enhancement
The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
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.
A global variable
i_am_root
is used to decide if the node is initialized as root or as a normal node. This approach makes it impossible to handle multiple dodags, because the device could be a normal node for one dodag and root for another.