linux-kernel - Re: [PATCH RESEND 0/2] Bluetooth: fix bdaddr quirks

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <168555962133.19706.9121953193856938504.git-patchwork-notify@kernel.org>
Date:   Wed, 31 May 2023 19:00:21 +0000
From:   patchwork-bot+bluetooth@...nel.org
To:     Johan Hovold <johan+linaro@...nel.org>
Cc:     marcel@...tmann.org, johan.hedberg@...il.com, luiz.dentz@...il.com,
        mka@...omium.org, linux-bluetooth@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 0/2] Bluetooth: fix bdaddr quirks

Hello:

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

On Wed, 31 May 2023 11:04:22 +0200 you wrote:
> These patches fix a couple of issues with the two bdaddr quirks:
> 
> The first one allows HCI_QUIRK_INVALID_BDADDR to be used with
> HCI_QUIRK_NON_PERSISTENT_SETUP.
> 
> The second patch restores the original semantics of the
> HCI_QUIRK_USE_BDADDR_PROPERTY so that the controller is marked as
> unconfigured when no device address is specified in the devicetree (as
> the quirk is documented to work).
> 
> [...]

Here is the summary with links:
  - [RESEND,1/2] Bluetooth: fix invalid-bdaddr quirk for non-persistent setup
    https://git.kernel.org/bluetooth/bluetooth-next/c/92776a7e761e
  - [RESEND,2/2] Bluetooth: fix use-bdaddr-property quirk
    https://git.kernel.org/bluetooth/bluetooth-next/c/6ac517d8cf8b

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