From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: hci_conn: Fix connection cleanup with BIG with 2 or more BIS
Date: Thu, 23 Oct 2025 21:40:09 +0000 [thread overview]
Message-ID: <176125560974.3260295.12869326879844121323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251022202941.1537413-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 22 Oct 2025 16:29:41 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes bis_cleanup not considering connections in BT_OPEN state
> before attempting to remove the BIG causing the following error:
>
> btproxy[20110]: < HCI Command: LE Terminate Broadcast Isochronous Group (0x08|0x006a) plen 2
> BIG Handle: 0x01
> Reason: Connection Terminated By Local Host (0x16)
> > HCI Event: Command Status (0x0f) plen 4
> LE Terminate Broadcast Isochronous Group (0x08|0x006a) ncmd 1
> Status: Unknown Advertising Identifier (0x42)
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: hci_conn: Fix connection cleanup with BIG with 2 or more BIS
https://git.kernel.org/bluetooth/bluetooth-next/c/990c0549b5f1
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:[~2025-10-23 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:29 [PATCH v1] Bluetooth: hci_conn: Fix connection cleanup with BIG with 2 or more BIS Luiz Augusto von Dentz
2025-10-22 20:50 ` Paul Menzel
2025-10-22 21:01 ` [v1] " bluez.test.bot
2025-10-23 21:40 ` 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=176125560974.3260295.12869326879844121323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).