Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-3881-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 RESEND 0/2] Bluetooth: qca: fix NULL-deref on non-serdev setup
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171379982888.28518.5007665871256276343.git-patchwork-notify@kernel.org>
Date: Mon, 22 Apr 2024 15:30:28 +0000
References: <20240422135748.23081-1-johan+linaro@kernel.org>
In-Reply-To: <20240422135748.23081-1-johan+linaro@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, jiangzp@google.com,
 linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org

Hello:

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

On Mon, 22 Apr 2024 15:57:46 +0200 you wrote:
> Qualcomm Bluetooth controllers can be registered either from a serdev
> driver or from the Bluetooth line discipline. In the latter case, the
> HCI UART serdev pointer is NULL, something which the driver needs to
> handle without crashing.
> 
> This series fixes one such issue at setup() time which incidentally
> masked a similar crash at suspend. Fix this in two separate patches so
> that the latter issue is addressed in pre-6.2 stable kernels.
> 
> [...]

Here is the summary with links:
  - [RESEND,1/2] Bluetooth: qca: fix NULL-deref on non-serdev suspend
    https://git.kernel.org/bluetooth/bluetooth-next/c/8185331e953d
  - [RESEND,2/2] Bluetooth: qca: fix NULL-deref on non-serdev setup
    https://git.kernel.org/bluetooth/bluetooth-next/c/9201f29be2c9

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