From: Val Packett <val@packett.cool>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: x1-dell-thena: Move PERST and Wake GPIOs to PCIe port nodes
Date: Thu, 12 Feb 2026 12:31:57 -0300 [thread overview]
Message-ID: <a5ec9742-e16d-4177-8250-46678fa19b98@packett.cool> (raw)
In-Reply-To: <2b1b38ef-3097-45c4-835d-d7e367f235b0@oss.qualcomm.com>
On 2/12/26 9:06 AM, Konrad Dybcio wrote:
> On 2/10/26 6:45 PM, Val Packett wrote:
>> Recently the DTs for most Hamoa-based devices received this change, but
>> the Thena dtsi (common for Dell Latitude and Inspiron SKUs) was skipped.
>> Apply the change to it.
>>
>> Fixes: 960609b22be5 ("arm64: dts: qcom: hamoa: Move PHY, PERST, and Wake GPIOs to PCIe port nodes and add port Nodes for all PCIe ports")
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> huh?
>
> Konrad
Oops! Sorry, I *completely* forgot the entire concept of versions somehow..
This was a v2: pull R-b and Fixes tags,
v1: https://lore.kernel.org/all/20260114203600.5617-1-val@packett.cool/
~val
next prev parent reply other threads:[~2026-02-12 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 17:45 [PATCH 1/2] arm64: dts: qcom: x1-dell-thena: Move PERST and Wake GPIOs to PCIe port nodes Val Packett
2026-02-10 17:45 ` [PATCH 2/2] arm64: dts: qcom: x1-dell-thena: remove i2c20 (battery SMBus) and reserve its pins Val Packett
2026-02-12 12:07 ` Konrad Dybcio
2026-02-12 12:06 ` [PATCH 1/2] arm64: dts: qcom: x1-dell-thena: Move PERST and Wake GPIOs to PCIe port nodes Konrad Dybcio
2026-02-12 15:31 ` Val Packett [this message]
2026-02-12 15:35 ` Konrad Dybcio
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=a5ec9742-e16d-4177-8250-46678fa19b98@packett.cool \
--to=val@packett.cool \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--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 \
--cc=ziyue.zhang@oss.qualcomm.com \
/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