From: Krzysztof Kozlowski <krzk@kernel.org>
To: jens.glathe@oldschoolsolutions.biz,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: x1-hp-x14: Commonalize HP Omnibook X14 device tree
Date: Thu, 3 Jul 2025 09:03:07 +0200 [thread overview]
Message-ID: <369fc807-f05e-4837-b623-b718e47fd840@kernel.org> (raw)
In-Reply-To: <20250703-hp-x14-x1p-v3-2-affe103b4356@oldschoolsolutions.biz>
On 03/07/2025 08:59, Jens Glathe via B4 Relay wrote:
> From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
>
> Commonalize the HP Omnibook X14 device tree for derivation of Hamoa (x1e*/x1p6*)
> and Purwa (x1p4*/x1*) variants. Required because the device trees are not
> compatible.
>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> ---
> arch/arm64/boot/dts/qcom/x1-hp-omnibook-x14.dtsi | 1549 ++++++++++++++++++++
> .../boot/dts/qcom/x1e80100-hp-omnibook-x14.dts | 1544 +------------------
Use proper -M/-B/-C arguments for git format-patch (b4 cannot do it in
the past), so this will be reviewable.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-03 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 6:59 [PATCH v3 0/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
2025-07-03 6:59 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Split HP Omnibook X14 AI in SoC variants Jens Glathe via B4 Relay
2025-07-03 7:02 ` Krzysztof Kozlowski
2025-07-03 6:59 ` [PATCH v3 2/3] arm64: dts: qcom: x1-hp-x14: Commonalize HP Omnibook X14 device tree Jens Glathe via B4 Relay
2025-07-03 7:03 ` Krzysztof Kozlowski [this message]
2025-07-03 6:59 ` [PATCH v3 3/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
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=369fc807-f05e-4837-b623-b718e47fd840@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--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;
as well as URLs for NNTP newsgroup(s).