-
Notifications
You must be signed in to change notification settings - Fork 8.3k
drivers: can: clarify the meaning of minimum/maximum supported bitrates #80127
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
Merged
aescolar
merged 1 commit into
zephyrproject-rtos:main
from
vestas-wind-systems:can_get_bitrate_min_doxygen
Oct 23, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
It's laudable to update the docs for the deprecated function -- it really is! -- but in this instance I wonder if it's not counter productive. Keeping the docs of the deprecated method as lean as possible helps make the
@deprecatedmention less buried in surrounding text.I think it's acceptable to let the docs of a deprecated method go stale since, after all, any new user is encouraged to look for the replacement. And to some extent I think it's ok that any existing user in need to look back at the docs to understand/clarify the behavior would basically see the docs as they were when it was decided to deprecate the method.
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.
Thank you for reviewing. I opted to keep the documentation in sync between the deprecated functions and their replacement to convey that there are no functional changes between the two.