[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83c6c3f6-ff6f-4e1c-8c20-78a13b0f85cd@oldschoolsolutions.biz>
Date: Tue, 8 Jul 2025 10:17:03 +0200
From: Jens Glathe <jens.glathe@...schoolsolutions.biz>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: arm: qcom: Split HP Omnibook X14 AI
in SoC variants
On 7/8/25 09:45, Krzysztof Kozlowski wrote:
> On Sat, Jul 05, 2025 at 10:31:54PM +0200, Jens Glathe wrote:
>> The HP Omnibook X14 AI PC is available in fe0 (Hamoa, x1e80100) and
>> fe1 (Purwa, x1p42100) SKUs. Since they are not completely dtb-compatible,
>> split the model strings in 2 variants:
>>
>> hp,omnibook-x14 compatible to qcom,x1e80100
>> hp,omnibook-x14-fe1 compatible to cqom,x1p42100
> I don't see split here. You are adding a new compatible for the fe1
> variant. It's fine to mention there is fe0 already, but main point of
> commit msg should express what you want to do and doing here.
Isn't the effect of creating 2 compatible strings for the same model
with different SKUs a split?
with best regards
Jens
Powered by blists - more mailing lists