| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id:
<171451391794.30746.12874463532882564623.git-patchwork-notify@kernel.org>
Date: Tue, 30 Apr 2024 21:51:57 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Johan Hovold <johan+linaro@...nel.org>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, dianders@...omium.org,
quic_janathot@...cinc.com, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] Bluetooth: qca: generalise device address check
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.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
Powered by blists - more mailing lists