From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jason Pettit <jason.pettit@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Akhil P Oommen <akhilpo@oss.qualcomm.com>,
Mahadevan P <mahadevan.p@oss.qualcomm.com>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Ananthu C V <ananthu.cv@oss.qualcomm.com>
Subject: Re: [PATCH 1/3] dt-bindings: arm: qcom: Add HP EliteBook X G2q 14 AI
Date: Sun, 21 Jun 2026 20:29:37 +0200 [thread overview]
Message-ID: <a4252886-112c-4b04-9216-d945572119d1@kernel.org> (raw)
In-Reply-To: <20260620-glymur-send-v1-1-fc4a2cfd107c@oss.qualcomm.com>
On 21/06/2026 06:50, Jason Pettit wrote:
> The HP EliteBook X G2q 14 AI is a Snapdragon X2 Elite (Glymur) laptop.
> Document its top-level "hp,elitebook-x-g2q" compatible, falling back to
> the existing "qcom,glymur" SoC compatible.
Drop last sentence. It's pointless to explain what the diff is doing.
>
> Signed-off-by: Jason Pettit <jason.pettit@oss.qualcomm.com>
> Assisted-by: Claude:claude-opus-4-8
Your tag is supposed to be the last one. And really, making such commit
with Claude feels odd. This is a single one liner.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-21 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 4:50 [PATCH 0/3] X2 Elite HP EliteBook X G2q support Jason Pettit
2026-06-21 4:50 ` [PATCH 1/3] dt-bindings: arm: qcom: Add HP EliteBook X G2q 14 AI Jason Pettit
2026-06-21 18:29 ` Krzysztof Kozlowski [this message]
2026-06-21 4:50 ` [PATCH 2/3] arm64: dts: " Jason Pettit
2026-06-21 5:08 ` sashiko-bot
2026-06-22 8:18 ` Abel Vesa
2026-06-22 9:23 ` Konrad Dybcio
2026-06-22 9:33 ` Konrad Dybcio
2026-06-21 4:50 ` [PATCH 3/3] firmware: qcom: scm: Allow QSEECOM on " Jason Pettit
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=a4252886-112c-4b04-9216-d945572119d1@kernel.org \
--to=krzk@kernel.org \
--cc=akhilpo@oss.qualcomm.com \
--cc=ananthu.cv@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason.pettit@oss.qualcomm.com \
--cc=jingyi.wang@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=mahadevan.p@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@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