From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings
Date: Thu, 07 Aug 2025 15:50:05 +0000 [thread overview]
Message-ID: <175458180551.3605358.14524802344851831054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250806194836.291949-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 6 Aug 2025 15:48:35 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> {cis,bis}_capable only indicates the controller supports the feature
> since it doesn't check that LE is enabled so it shall not be used for
> current setting, instead this introduces {cis,bis}_enabled macros that
> can be used to indicate that these features are currently enabled.
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings
https://git.kernel.org/bluetooth/bluetooth-next/c/3ca23aaba210
- [v3,2/2] Bluetooth: hci_core: Fix using ll_privacy_capable for current settings
https://git.kernel.org/bluetooth/bluetooth-next/c/c244fc08ac4e
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-08-07 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 19:48 [PATCH v3 1/2] Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings Luiz Augusto von Dentz
2025-08-06 19:48 ` [PATCH v3 2/2] Bluetooth: hci_core: Fix using ll_privacy_capable " Luiz Augusto von Dentz
2025-08-07 8:01 ` Paul Menzel
2025-08-06 20:37 ` [v3,1/2] Bluetooth: hci_core: Fix using {cis,bis}_capable " bluez.test.bot
2025-08-07 8:01 ` [PATCH v3 1/2] " Paul Menzel
2025-08-07 15: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=175458180551.3605358.14524802344851831054.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 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.