-
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
auto_init: fix array-initializer order for gnrc_netdev2 stacks #6312
auto_init: fix array-initializer order for gnrc_netdev2 stacks #6312
Conversation
could you also fix for the |
Fixed |
Rebased |
71d00d9
to
65e5fac
Compare
Nice catch! |
Would you rebase so we can also see Jeniks working? |
65e5fac
to
a4d421a
Compare
Rebased. |
@miri64 please squash |
a4d421a
to
82d8d3d
Compare
done |
@haukepetersen your review was requested. Changes were addressed and Murdock/Jenkins succeeded. Pleas merge! |
Anyone willing to ACK? |
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.
ACK
and go. |
While working on #6311 I noticed, that quite a few stacks arrays for the gnrc_netdev2 auto-initialization have their initializers switched around. This leads to faulty code, since apart from a few byte all threads will have the same stack (and TCB) which leads to funny errors, like only the last initialized thread answering to IPC messages of all devices of that type.