From: Bjorn Andersson <andersson@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v1 0/2] X1E HBR3 fixes
Date: Mon, 11 Aug 2025 22:04:43 -0500 [thread overview]
Message-ID: <175496788909.165980.10869456237314357740.b4-ty@kernel.org> (raw)
In-Reply-To: <20250630205514.14022-1-alex.vinarskis@gmail.com>
On Mon, 30 Jun 2025 22:54:09 +0200, Aleksandrs Vinarskis wrote:
> It appears during initial series to enable HBR3 earlier this year [1]
> few devices were left out, add them.
>
> [1] https://lore.kernel.org/all/20250226231436.16138-1-alex.vinarskis@gmail.com/
>
> Aleksandrs Vinarskis (2):
> arm64: dts: qcom: x1-crd: Enable HBR3 on external DPs
> arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Enable HBR3 on
> external DPs
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: x1-crd: Enable HBR3 on external DPs
commit: 60fdba1dccd81420bbe8da0d7483b4f28c7fa833
[2/2] arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Enable HBR3 on external DPs
commit: 93109afda01593c2ddadb4ec1c42b3bdf695ee2a
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-08-12 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 20:54 Aleksandrs Vinarskis
2025-06-30 20:54 ` [PATCH v1 1/2] arm64: dts: qcom: x1-crd: Enable HBR3 on external DPs Aleksandrs Vinarskis
2025-06-30 20:54 ` [PATCH v1 2/2] arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: " Aleksandrs Vinarskis
2025-07-01 10:56 ` [PATCH v1 0/2] X1E HBR3 fixes Konrad Dybcio
2025-07-17 10:21 ` Aleksandrs Vinarskis
2025-08-12 3:04 ` Bjorn Andersson [this message]
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=175496788909.165980.10869456237314357740.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=alex.vinarskis@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®