[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d21a6d94-d2bc-44fd-bf40-097bccc11930@kernel.org>
Date: Thu, 6 Mar 2025 12:56:02 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Varadarajan Narayanan <quic_varada@...cinc.com>, bhelgaas@...gle.com,
lpieralisi@...nel.org, kw@...ux.com, manivannan.sadhasivam@...aro.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, vkoul@...nel.org,
kishon@...nel.org, andersson@...nel.org, konradybcio@...nel.org,
p.zabel@...gutronix.de, quic_nsekar@...cinc.com,
dmitry.baryshkov@...aro.org, linux-arm-msm@...r.kernel.org,
linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-phy@...ts.infradead.org
Subject: Re: [PATCH v11 4/7] arm64: dts: qcom: ipq9574: Reorder reg and
reg-names
On 06/03/2025 12:49, Krzysztof Kozlowski wrote:
> On 20/02/2025 10:42, Varadarajan Narayanan wrote:
>> The 'reg' & 'reg-names' constraints used in the bindings and dtsi are
>> different resulting in dt_bindings_check errors. Re-order the reg entries,
>
> Why?
>
>> fix the node names and move the nodes to maintain sort order to address the
>
> Fixing (how?) node name looks like separate problem.
>
>
>> following errors/warnings.
>>
>> arch/arm64/boot/dts/qcom/ipq9574-rdp449.dtb: pcie@...00000: reg-names:0: 'parf' was expected
How can I reproduce this error?
Isn't this error which you intentionally added and now you claim you
fix? In the same patchset?
This really looks like breaking things just to call it "look, I fixed
something" two patches later in the same set.
Best regards,
Krzysztof
Powered by blists - more mailing lists