-
Notifications
You must be signed in to change notification settings - Fork 8.2k
fix ring_buf designated initializer order for RING_BUF_DECLARE #45698
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
fix ring_buf designated initializer order for RING_BUF_DECLARE #45698
Conversation
stephanosio
left a comment
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.
Thanks for submitting this PR.
Please review the Contribution Guidelines.
stephanosio
left a comment
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.
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "fix ring_buf designated initializer order for RING_BUF_DECLARE"
1: UC6 Body has no content, should at least have 1 line.
Please review https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines.
480c17a to
472dc2d
Compare
Change order of designated initializers for ring_buf struct in the RING_BUF_DECLARE macro, to match the order in the struct definition. This fixes compilation when using C++, which requires using the same order as in the struct definition. Fixes zephyrproject-rtos#45697 Signed-off-by: Jonas Otto <[email protected]>
stephanosio
left a comment
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.
Thanks!
fixes #45697