Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-5241-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] Bluetooth: qca: Fix BT enable failure again for QCA6390
 after warm reboot
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171803462799.21636.13193353610709896415.git-patchwork-notify@kernel.org>
Date: Mon, 10 Jun 2024 15:50:27 +0000
References: <1715866294-1549-1-git-send-email-quic_zijuhu@quicinc.com>
In-Reply-To: <1715866294-1549-1-git-send-email-quic_zijuhu@quicinc.com>
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, luiz.von.dentz@intel.com, marcel@holtmann.org,
 linux-bluetooth@vger.kernel.org, wt@penguintechs.org,
 regressions@lists.linux.dev, pmenzel@molgen.mpg.de,
 krzysztof.kozlowski@linaro.org, lk_sii@163.com, stable@vger.kernel.org

Hello:

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

On Thu, 16 May 2024 21:31:34 +0800 you wrote:
> Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed
> serdev") will cause below regression issue:
> 
> BT can't be enabled after below steps:
> cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure
> if property enable-gpios is not configured within DT|ACPI for QCA6390.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot
    https://git.kernel.org/bluetooth/bluetooth-next/c/d2118673f3ae

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