[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae1a2220-7494-4f7e-ac23-f0b2aebeee75@quicinc.com>
Date: Sat, 27 Jan 2024 13:13:10 +0530
From: Krishna Kurapati PSSNV <quic_kriskura@...cinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Bjorn Andersson
<andersson@...nel.org>
CC: Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring
<robh+dt@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Conor Dooley
<conor+dt@...nel.org>,
Johan Hovold <johan+linaro@...nel.org>,
<cros-qcom-dts-watchers@...omium.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<quic_ppratap@...cinc.com>, <quic_jackp@...cinc.com>
Subject: Re: [PATCH v2 1/4] arm64: dts: qcom: Fix hs_phy_irq for QUSB2 targets
>
> v1.4.0? I am sorry, but what?
>
> Isn't that like 10 years old? What systems are you using there? I am
> asking, because maybe we should be rejecting DTS patches assuming they
> were never tested (testing on ancient dtc counts like no testing).
>
>> When I moved to 1.5.0, I did see these warnings. Fixed them up and sent v3.
>
> Nope, you just moved from 10 years old to 5 years old.
>
> Fix your systems and use the recent one. v1.6.1
>
Hi Krzysztof,
It was an old pc I was using this time and it was using local
/usr/bin/dtc for some reason. I got the latest version working:
kriskura@...kriskura-hyd:/local/mnt/workspace/krishna/skales_dt_cleanup/skales/kernel$
dtc -v
Version: DTC 1.6.1-gabbd523b
And with this version, I don't see any errors in the v3 pushed.
Thanks,
Krishna,
Powered by blists - more mailing lists