All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Johan Hovold <johan+linaro@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, mka@chromium.org,
	dianders@chromium.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, quic_janathot@quicinc.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: qca: fix invalid device address check
Date: Tue, 16 Apr 2024 15:10:34 +0000	[thread overview]
Message-ID: <171328023410.16225.6796027488142953241.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240416091509.19995-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 Tue, 16 Apr 2024 11:15:09 +0200 you wrote:
> Qualcomm Bluetooth controllers may not have been provisioned with a
> valid device address and instead end up using the default address
> 00:00:00:00:5a:ad.
> 
> This was previously believed to be due to lack of persistent storage for
> the address but it may also be due to integrators opting to not use the
> on-chip OTP memory and instead store the address elsewhere (e.g. in
> storage managed by secure world firmware).
> 
> [...]

Here is the summary with links:
  - Bluetooth: qca: fix invalid device address check
    https://git.kernel.org/bluetooth/bluetooth-next/c/00567f70051a

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-04-16 15:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  9:15 [PATCH] Bluetooth: qca: fix invalid device address check Johan Hovold
2024-04-16  9:56 ` bluez.test.bot
2024-04-16 15:10 ` patchwork-bot+bluetooth [this message]
2024-04-22 17:50 ` [PATCH] " Doug Anderson
2024-04-23  9:08   ` Johan Hovold
2024-04-23 15:09     ` Doug Anderson
2024-04-25  8:40       ` Johan Hovold
2024-04-25 15:01         ` Janaki Ramaiah Thota
2024-04-25 15:58           ` Johan Hovold
2024-04-26  6:23             ` Janaki Ramaiah Thota
2024-04-26 10:42               ` Janaki Ramaiah Thota
2024-04-26 12:45                 ` Johan Hovold
2024-04-26 14:15                   ` Johan Hovold
2024-04-25 15:22         ` Doug Anderson
2024-04-25 16:13           ` Johan Hovold
2024-04-25 16:19             ` Doug Anderson

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=171328023410.16225.6796027488142953241.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=dianders@chromium.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=mka@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.