Bluetooth: L2CAP: document memset requirement #76890
Merged
Conversation
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
The `struct bt_l2cap_le_chan` and `struct bt_l2cap_br_chan` objects should be memset before passing them to the stack. This was not stated anywhere, but all the in-tree users are doing it, so it must be API. Signed-off-by: Jonathan Rico <[email protected]>
zephyrbot
added
area: Bluetooth Host
theob-pro
approved these changes
Aug 9, 2024
jhedberg
approved these changes
Aug 9, 2024
|
related #76935 |
alwa-nordic
approved these changes
Aug 12, 2024
@jhedberg Do I need to add a backport label or something? |
Unless you want to manually construct a backport PR, yes. I just added the label :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
struct bt_l2cap_le_chanandstruct bt_l2cap_br_chanobjects should be memset before passing them to the stack.This was not stated anywhere, but all the in-tree users are doing it, so it must be API.
#docfixFixes #76737