From: patchwork-bot+bluetooth@kernel.org
To: Tobias Wilken <tooangel@tooangel.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] doc: Add CONFIG_RFKILL to the tester kernel config
Date: Fri, 23 Oct 2026 22:20:11 +0000 [thread overview]
Message-ID: <179279401107.1297354.6783483439385343291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021072133.136948-1-tooangel@tooangel.de>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 21 Oct 2026 09:21:32 +0200 you wrote:
> Needed by mgmt-tester to block a controller through /dev/rfkill.
>
> Assisted-by: Claude:claude-opus-5-5
> ---
>
> Notes:
> As far as I understand, this is needed for the following mgmt-tester
> patch: without CONFIG_RFKILL its new test is skipped instead of run.
> Please correct me if I'm wrong.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] doc: Add CONFIG_RFKILL to the tester kernel config
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=48bb3b396980
- [BlueZ,2/2] mgmt-tester: Add Set Powered test for rfkill block
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1445a64e6b99
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:[~2026-10-23 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 7:21 [PATCH BlueZ 1/2] doc: Add CONFIG_RFKILL to the tester kernel config Tobias Wilken
2026-10-21 7:21 ` [PATCH BlueZ 2/2] mgmt-tester: Add Set Powered test for rfkill block Tobias Wilken
2026-10-21 8:29 ` [BlueZ,1/2] doc: Add CONFIG_RFKILL to the tester kernel config bluez.test.bot
2026-10-23 22:20 ` 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=179279401107.1297354.6783483439385343291.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tooangel@tooangel.de \
/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.