All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: ISO: consider right CIS when removing CIG at cleanup
Date: Mon, 22 May 2023 21:10:19 +0000	[thread overview]
Message-ID: <168478981941.2048.3358211127005602203.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2bf70b0560375b50180518968abd8c4dfcce7f34.1684788145.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 Mon, 22 May 2023 20:52:44 +0000 you wrote:
> When looking for CIS blocking CIG removal, consider only the CIS with
> the right CIG ID. Don't try to remove CIG with unset CIG ID.
> 
> Fixes: 26afbd826ee3 ("Bluetooth: Add initial implementation of CIS connections")
> Signed-off-by: Pauli Virtanen <pav@iki.fi>
> ---
> 
> [...]

Here is the summary with links:
  - [v2,1/2] Bluetooth: ISO: consider right CIS when removing CIG at cleanup
    (no matching commit)
  - [v2,2/2] Bluetooth: ISO: fix CIG auto-allocation to select configurable CIG
    https://git.kernel.org/bluetooth/bluetooth-next/c/fb576dc48252

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-05-22 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 20:52 [PATCH v2 1/2] Bluetooth: ISO: consider right CIS when removing CIG at cleanup Pauli Virtanen
2023-05-22 20:52 ` [PATCH v2 2/2] Bluetooth: ISO: fix CIG auto-allocation to select configurable CIG Pauli Virtanen
2023-05-22 21:10 ` patchwork-bot+bluetooth [this message]
2023-05-22 21:48 ` [v2,1/2] Bluetooth: ISO: consider right CIS when removing CIG at cleanup bluez.test.bot

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=168478981941.2048.3358211127005602203.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.