From: patchwork-bot+bluetooth@kernel.org
To: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
kiran.k@intel.com, chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v10 0/2] Bluetooth: add hardware rfkill handling
Date: Fri, 16 Oct 2026 15:40:14 +0000 [thread overview]
Message-ID: <179216521476.826981.15138353307358957117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016025921.1719986-1-aluvala.sai.teja@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 16 Oct 2026 08:29:19 +0530 you wrote:
> This series adds hardware rfkill handling for the Intel PCIe transport
> and the Bluetooth-side notification path.
>
> The resulting flow is:
>
> transport hardware event
> -> hci_rfkill_set_hw_state()
> -> rfkill hardware state
> -> hdev->rfkill_block work
> -> HCI_RFKILLED state and device power handling
>
> [...]
Here is the summary with links:
- [v10,1/2] Bluetooth: Add HCI interface for HW rfkill events
https://git.kernel.org/bluetooth/bluetooth-next/c/09399227b038
- [v10,2/2] Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow
https://git.kernel.org/bluetooth/bluetooth-next/c/f600f753cc32
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-16 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 2:59 [PATCH v10 0/2] Bluetooth: add hardware rfkill handling Sai Teja Aluvala
2026-10-16 2:59 ` [PATCH v10 1/2] Bluetooth: Add HCI interface for HW rfkill events Sai Teja Aluvala
2026-10-16 5:48 ` Bluetooth: add hardware rfkill handling bluez.test.bot
2026-10-16 2:59 ` [PATCH v10 2/2] Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow Sai Teja Aluvala
2026-10-16 15: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=179216521476.826981.15138353307358957117.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aluvala.sai.teja@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--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