[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170474342471.29412.9439877422079885487.git-patchwork-notify@kernel.org>
Date: Mon, 08 Jan 2024 19:50:24 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Jonas Dreßler <verdre@...d.nl>@codeaurora.org
Cc: marcel@...tmann.org, johan.hedberg@...il.com, luiz.dentz@...il.com,
asahi@...ts.linux.dev, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v2 0/4] Power off HCI devices before rfkilling them
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Tue, 2 Jan 2024 19:19:16 +0100 you wrote:
> In theory the firmware is supposed to power off the bluetooth card
> when we use rfkill to block it. This doesn't work on a lot of laptops
> though, leading to weird issues after turning off bluetooth, like the
> connection timing out on the peripherals which were connected, and
> bluetooth not connecting properly when the adapter is turned on again
> quickly after rfkilling.
>
> [...]
Here is the summary with links:
- [v2,1/4] Bluetooth: Remove HCI_POWER_OFF_TIMEOUT
https://git.kernel.org/bluetooth/bluetooth-next/c/f48705f473ce
- [v2,2/4] Bluetooth: mgmt: Remove leftover queuing of power_off work
https://git.kernel.org/bluetooth/bluetooth-next/c/2e7a6a997c9a
- [v2,3/4] Bluetooth: Add new state HCI_POWERING_DOWN
https://git.kernel.org/bluetooth/bluetooth-next/c/2b16c80d8011
- [v2,4/4] Bluetooth: Queue a HCI power-off command before rfkilling adapters
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists