Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-3228-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ 0/1] V3: Fix busy loop when disabling BT
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171225663071.19551.11859340308005262666.git-patchwork-notify@kernel.org>
Date: Thu, 04 Apr 2024 18:50:30 +0000
References: <20240404183050.334414-1-dimitris.on.linux@gmail.com>
In-Reply-To: <20240404183050.334414-1-dimitris.on.linux@gmail.com>
To: Dimitris <dimitris.on.linux@gmail.com>
Cc: linux-bluetooth@vger.kernel.org

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  4 Apr 2024 11:30:49 -0700 you wrote:
> Splitting the service state test out of btd_device_is_connected
> and using only the bearer-specific test from adapter_remove_connection.
> 
> This intends to fix a busy loop that happens when BT is disabled
> from userspace with e.g. "rfkill block bluetooth":
> 
> 1. Connect at least one device.
> 2. Run rfkill block bluetooth.
> 3. bluetoothd takes 100% CPU.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] refactor bearer connected test
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=036583f9bbec

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html