-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
mgmt: mcumgr: Deprecate returning rc responses when status is OK. #51555
Conversation
98c44d1
to
b4c8a0c
Compare
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.
No need to deprecate, this is unstable. Please remove it altogether so we can declare it stable soon.
With this change it's more to give users the choice to revert as some software that uses that might be unable to cope with the change, and they might need time to adapt the software. |
Yes, but @nordicjm mentions important issue of no-Zephyr based tools, that may require some time to adapt. |
This change changes the previous mcumgr behaviour of return result codes when the status is 0 (OK) to being legacy behaviour, instead it will skip the rc field for these responses. If there is only an rc field with status 0 to return, then mcumgr will now instead just return an empty map. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note on rc responses to mcumgr commands where the status is good that these responses will henceforth be emitted. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Updates documentation on when the rc response is returned. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
@carlescufi Please take another look. Thanks. |
This change deprecates the previous mcumgr behaviour of return result codes when the status is 0 (OK), instead it will skip the rc field for these responses. If there is only an rc field with status 0 to return, then mcumgr will now instead just return an empty map.
Fixes #42590