Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-4201-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 v2 0/3] Bluetooth: qca: generalise device address check
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171451391794.30746.12874463532882564623.git-patchwork-notify@kernel.org>
Date: Tue, 30 Apr 2024 21:51:57 +0000
References: <20240430170741.15742-1-johan+linaro@kernel.org>
In-Reply-To: <20240430170741.15742-1-johan+linaro@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, dianders@chromium.org,
 quic_janathot@quicinc.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 Tue, 30 Apr 2024 19:07:38 +0200 you wrote:
> The QCA default device address apparently comes from the NVM
> configuration file and can differ quite a bit between controllers.
> 
> This series adds support for storing the default address when parsing
> the configuration file and using it to determine whether the controller
> has been provisioned with an address.
> 
> [...]

Here is the summary with links:
  - [v2,1/3] Bluetooth: qca: add missing firmware sanity checks
    https://git.kernel.org/bluetooth/bluetooth-next/c/fd10f4fe66a1
  - [v2,2/3] Bluetooth: qca: fix NVM configuration parsing
    https://git.kernel.org/bluetooth/bluetooth-next/c/882125a9cdb9
  - [v2,3/3] Bluetooth: qca: generalise device address check
    https://git.kernel.org/bluetooth/bluetooth-next/c/aa63c8b7b1c2

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