From: patchwork-bot+bluetooth@kernel.org
To: Tobias Wilken <tooangel@tooangel.de>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller
Date: Fri, 23 Oct 2026 22:10:11 +0000 [thread overview]
Message-ID: <179279341105.1294506.2700531975523429266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021065833.120347-1-tooangel@tooangel.de>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 21 Oct 2026 08:58:33 +0200 you wrote:
> Since MGMT_OP_SET_POWERED runs through hci_cmd_sync, powering on a
> controller that is blocked by rfkill fails with -ERFKILL from
> hci_dev_open_sync(), and mgmt_set_powered_complete() reports it with
> mgmt_status(err). mgmt_errno_status() has no case for -ERFKILL, so
> userspace gets MGMT_STATUS_FAILED instead of MGMT_STATUS_RFKILLED.
>
> Before that conversion, power on went through hci_power_on(), whose
> error path mgmt_set_powered_failed() still maps -ERFKILL to
> MGMT_STATUS_RFKILLED. bluetoothd relies on that status: for
> RFKILLED it sets the adapter PowerState to "off-blocked" and returns
> org.bluez.Error.Blocked for the Powered property, for any other status
> it returns org.bluez.Error.Failed.
>
> [...]
Here is the summary with links:
- Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller
https://git.kernel.org/bluetooth/bluetooth-next/c/65683fbed5c8
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:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:58 Tobias Wilken
2026-10-23 22:10 ` 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=179279341105.1294506.2700531975523429266.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®