public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org, johan+linaro@kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: Patch "arm64: dts: qcom: qcs404: fix bluetooth device address" has been added to the 5.4-stable tree
Date: Tue, 25 Jun 2024 08:27:21 +0200	[thread overview]
Message-ID: <ZnpjSVGrN7kJMuhx@hovoldconsulting.com> (raw)
In-Reply-To: <20240625033042.1608217-1-sashal@kernel.org>

On Mon, Jun 24, 2024 at 11:30:42PM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     arm64: dts: qcom: qcs404: fix bluetooth device address
> 
> to the 5.4-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

> commit a48b0e85558565dc3a10c8021b1514099cada102
> Author: Johan Hovold <johan+linaro@kernel.org>
> Date:   Wed May 1 09:52:01 2024 +0200
> 
>     arm64: dts: qcom: qcs404: fix bluetooth device address
>     
>     [ Upstream commit f5f390a77f18eaeb2c93211a1b7c5e66b5acd423 ]
>     
>     The 'local-bd-address' property is used to pass a unique Bluetooth
>     device address from the boot firmware to the kernel and should otherwise
>     be left unset so that the OS can prevent the controller from being used
>     until a valid address has been provided through some other means (e.g.
>     using btmgmt).
>     
>     Fixes: 60f77ae7d1c1 ("arm64: dts: qcom: qcs404-evb: Enable uart3 and add Bluetooth")
>     Cc: stable@vger.kernel.org      # 5.10

This was supposed to say 5.2. Thanks for catching this.

Johan

           reply	other threads:[~2024-06-25  6:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240625033042.1608217-1-sashal@kernel.org>]

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=ZnpjSVGrN7kJMuhx@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --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