From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jens Glathe <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,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH v7 2/3] arm64: dts: qcom: x1-hp-x14: Unify HP Omnibook X14 device tree structure
Date: Thu, 10 Jul 2025 15:25:58 +0200 [thread overview]
Message-ID: <aa94dcb8-8a9a-407e-9bab-39a321a7136b@kernel.org> (raw)
In-Reply-To: <056c3569-02d7-4668-89d0-91a8d92814ef@oldschoolsolutions.biz>
On 10/07/2025 13:31, Jens Glathe wrote:
> On 10.07.25 12:55, Krzysztof Kozlowski wrote:
>> Why am I bothering to review if you keep changing and eventually
>> dropping the tag.
>
> Sorry about that. b4 didn't take it, and since I changed the commit
> message after Bryan made the suggestion, didn't know if it was still
> justified.
>
It takes for me. b4 shazam -v6:
[PATCH v6 1/3] dt-bindings: arm: qcom: Add HP Omnibook X14 AI X1P4200 variant
+ Link: https://lore.kernel.org/r/20250709-hp-x14-x1p-v6-1-f45cc186a62d@oldschoolsolutions.biz
[PATCH v6 2/3] arm64: dts: qcom: x1-hp-x14: Commonalize HP Omnibook X14 device tree
+ Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> (✓ DKIM/kernel.org)
+ Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> (✓ DKIM/qualcomm.com)
+ Link: https://lore.kernel.org/r/20250709-hp-x14-x1p-v6-2-f45cc186a62d@oldschoolsolutions.biz
[PATCH v6 3/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14
+ Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> (✓ DKIM/kernel.org)
+ Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> (✓ DKIM/qualcomm.com)
+ Link: https://lore.kernel.org/r/20250709-hp-x14-x1p-v6-3-f45cc186a62d@oldschoolsolutions.biz
All tags are there.
If b4 misses it, you should add it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-10 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 10:50 [PATCH v7 0/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
2025-07-10 10:50 ` [PATCH v7 1/3] dt-bindings: arm: qcom: Add HP Omnibook X14 AI X1P4200 variant Jens Glathe via B4 Relay
2025-07-10 10:50 ` [PATCH v7 2/3] arm64: dts: qcom: x1-hp-x14: Unify HP Omnibook X14 device tree structure Jens Glathe via B4 Relay
2025-07-10 10:55 ` Krzysztof Kozlowski
2025-07-10 11:31 ` Jens Glathe
2025-07-10 13:25 ` Krzysztof Kozlowski [this message]
2025-07-10 13:45 ` Jens Glathe
2025-07-10 12:31 ` Konrad Dybcio
2025-09-09 16:07 ` Bjorn Andersson
2025-09-13 17:46 ` Jens Glathe
2025-07-10 10:50 ` [PATCH v7 3/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
2025-07-10 12:30 ` Konrad Dybcio
2025-07-10 10:53 ` [PATCH v7 0/3] " Krzysztof Kozlowski
2025-09-16 16:58 ` Bjorn Andersson
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=aa94dcb8-8a9a-407e-9bab-39a321a7136b@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.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
all inboxes | Powered by JetHome®