Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
RIOT
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cm-projects
RIOT
Commits
eb202ffe
Commit
eb202ffe
authored
10 years ago
by
Cenk Gündoğan
Browse files
Options
Downloads
Patches
Plain Diff
rpl: remove unsused warning
parent
c91cdcd4
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
sys/net/routing/rpl/rpl.c
+2
-0
2 additions, 0 deletions
sys/net/routing/rpl/rpl.c
with
2 additions
and
0 deletions
sys/net/routing/rpl/rpl.c
+
2
−
0
View file @
eb202ffe
...
@@ -62,7 +62,9 @@ static void _dao_handle_send(rpl_dodag_t *dodag);
...
@@ -62,7 +62,9 @@ static void _dao_handle_send(rpl_dodag_t *dodag);
static
void
_rpl_update_routing_table
(
void
);
static
void
_rpl_update_routing_table
(
void
);
#if RPL_DEFAULT_MOP == RPL_NON_STORING_MODE
#if RPL_DEFAULT_MOP == RPL_NON_STORING_MODE
#if RPL_MAX_ROUTING_ENTRIES != 0
static
uint8_t
srh_buffer
[
BUFFER_SIZE
];
static
uint8_t
srh_buffer
[
BUFFER_SIZE
];
#endif
static
uint8_t
srh_send_buffer
[
BUFFER_SIZE
];
static
uint8_t
srh_send_buffer
[
BUFFER_SIZE
];
static
ipv6_addr_t
*
down_next_hop
;
static
ipv6_addr_t
*
down_next_hop
;
static
ipv6_srh_t
*
srh_header
;
static
ipv6_srh_t
*
srh_header
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment