From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: hci_event: drop only unbound CIS if Set CIG Parameters fails
Date: Mon, 07 Aug 2023 23:50:23 +0000 [thread overview]
Message-ID: <169145222305.5057.17030807199575322111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5af5d6830d65173124aa525dd01b2718548ffb65.1691251325.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 5 Aug 2023 19:08:41 +0300 you wrote:
> When user tries to connect a new CIS when its CIG is not configurable,
> that connection shall fail, but pre-existing connections shall not be
> affected. However, currently hci_cc_le_set_cig_params deletes all CIS
> of the CIG on error so it doesn't work, even though controller shall not
> change CIG/CIS configuration if the command fails.
>
> Fix by failing on command error only the connections that are not yet
> bound, so that we keep the previous CIS configuration like the
> controller does.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: hci_event: drop only unbound CIS if Set CIG Parameters fails
https://git.kernel.org/bluetooth/bluetooth-next/c/f5669a036ae6
- [2/2] Bluetooth: hci_conn: avoid checking uninitialized CIG/CIS ids
https://git.kernel.org/bluetooth/bluetooth-next/c/6130cdd83d40
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-07 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 16:08 [PATCH 1/2] Bluetooth: hci_event: drop only unbound CIS if Set CIG Parameters fails Pauli Virtanen
2023-08-05 16:08 ` [PATCH 2/2] Bluetooth: hci_conn: avoid checking uninitialized CIG/CIS ids Pauli Virtanen
2023-08-05 16:41 ` [1/2] Bluetooth: hci_event: drop only unbound CIS if Set CIG Parameters fails bluez.test.bot
2023-08-07 23:50 ` patchwork-bot+bluetooth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169145222305.5057.17030807199575322111.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.