Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-3635-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: qca: fix invalid device address check
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171328023410.16225.6796027488142953241.git-patchwork-notify@kernel.org>
Date: Tue, 16 Apr 2024 15:10:34 +0000
References: <20240416091509.19995-1-johan+linaro@kernel.org>
In-Reply-To: <20240416091509.19995-1-johan+linaro@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, mka@chromium.org,
 dianders@chromium.org, linux-bluetooth@vger.kernel.org,
 linux-kernel@vger.kernel.org, quic_janathot@quicinc.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 Tue, 16 Apr 2024 11:15:09 +0200 you wrote:
> Qualcomm Bluetooth controllers may not have been provisioned with a
> valid device address and instead end up using the default address
> 00:00:00:00:5a:ad.
> 
> This was previously believed to be due to lack of persistent storage for
> the address but it may also be due to integrators opting to not use the
> on-chip OTP memory and instead store the address elsewhere (e.g. in
> storage managed by secure world firmware).
> 
> [...]

Here is the summary with links:
  - Bluetooth: qca: fix invalid device address check
    https://git.kernel.org/bluetooth/bluetooth-next/c/00567f70051a

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