[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7a552f24-50df-4c94-9bda-50712fc72485@linaro.org>
Date: Thu, 17 Jul 2025 08:33:27 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Luca Weiss <luca.weiss@...rphone.com>,
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] dt-bindings: arm: qcom-soc: Document new Milos and Glymur
SoCs
On 17/07/2025 08:27, Luca Weiss wrote:
> On Wed Jul 16, 2025 at 6:24 PM CEST, Krzysztof Kozlowski wrote:
>> Extend the schema enforcing correct SoC-block naming to cover Milos
>> (compatibles already accepted by some maintainers for next release) and
>> Glymur (posted on mailing lists [1]) SoCs.
>>
>> Link: https://lore.kernel.org/linux-devicetree/20250716152017.4070029-1-pankaj.patil@oss.qualcomm.com/ [1]
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>
>> ---
>>
>> I asked for documenting the Milos name at v2 of Milos patchset... it did
>> not happen and patches are already being accepted.
>
> Sorry about that, I seem to have missed that.
>
> However I did not see any dt validation errors with my milos dts or
> dt_binding_check on the bindings, where are these patterns relevant, in
> case I should touch it again in the future?
There would not be any errors, because how these bindings are written -
to ignore other, unknown names.
Best regards,
Krzysztof
Powered by blists - more mailing lists