linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Johan Hovold <johan+linaro@kernel.org>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, quic_janathot@quicinc.com
Subject: Re: [PATCH] Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT"
Date: Tue, 26 Mar 2024 15:30:40 +0000	[thread overview]
Message-ID: <171146704035.9961.13096206001570615153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240314084412.1127-1-johan+linaro@kernel.org>

Hello:

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

On Thu, 14 Mar 2024 09:44:12 +0100 you wrote:
> This reverts commit 7dcd3e014aa7faeeaf4047190b22d8a19a0db696.
> 
> Qualcomm Bluetooth controllers like WCN6855 do not have persistent
> storage for the Bluetooth address and must therefore start as
> unconfigured to allow the user to set a valid address unless one has
> been provided by the boot firmware in the devicetree.
> 
> [...]

Here is the summary with links:
  - Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT"
    https://git.kernel.org/bluetooth/bluetooth-next/c/ac0cf3552972

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



  parent reply	other threads:[~2024-03-26 15:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  8:44 [PATCH] Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT" Johan Hovold
2024-03-14 14:30 ` Luiz Augusto von Dentz
2024-03-14 15:07   ` Johan Hovold
2024-03-25 13:57     ` Linux regression tracking (Thorsten Leemhuis)
2024-03-25 17:10       ` Luiz Augusto von Dentz
2024-03-25 17:24         ` Johan Hovold
2024-03-25 19:39           ` Luiz Augusto von Dentz
2024-03-25 19:48             ` Johan Hovold
2024-03-25 20:07               ` Luiz Augusto von Dentz
2024-03-25 20:14                 ` Johan Hovold
2024-03-25 20:31                   ` Luiz Augusto von Dentz
2024-03-26  7:09                     ` Johan Hovold
2024-03-26 14:17                       ` Luiz Augusto von Dentz
2024-03-26 15:18                         ` Johan Hovold
2024-03-26 16:20                           ` Johan Hovold
2024-03-26 16:58                             ` Luiz Augusto von Dentz
2024-03-26 17:08                               ` Johan Hovold
2024-03-14 17:01 ` Clayton Craft
2024-03-26 15:30 ` patchwork-bot+bluetooth [this message]
2024-03-28 14:55   ` Janaki Ramaiah Thota
2024-03-28 15:23     ` Johan Hovold
2024-03-29  7:25       ` Janaki Ramaiah Thota
2024-04-03 12:24         ` Johan Hovold
2024-04-05 12:59           ` Janaki Ramaiah Thota
2024-04-15 10:52             ` Janaki Ramaiah Thota
2024-04-15 11:20               ` Johan Hovold
2024-04-16  9:20                 ` Johan Hovold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171146704035.9961.13096206001570615153.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=quic_janathot@quicinc.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).