Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH RESEND 0/2] Bluetooth: fix bdaddr quirks
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <168555962133.19706.9121953193856938504.git-patchwork-notify@kernel.org>
Date:   Wed, 31 May 2023 19:00:21 +0000
References: <20230531090424.3187-1-johan+linaro@kernel.org>
In-Reply-To: <20230531090424.3187-1-johan+linaro@kernel.org>
To:     Johan Hovold <johan+linaro@kernel.org>
Cc:     marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        mka@chromium.org, linux-bluetooth@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.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