[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73921d66-8258-4f82-95a8-f4e9fe8acc8e@oss.qualcomm.com>
Date: Wed, 20 Aug 2025 11:36:15 +0530
From: Raviteja Laggyshetty <raviteja.laggyshetty@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Georgi Djakov <djakov@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Mike Tipton <mike.tipton@....qualcomm.com>, linux-arm-msm@...r.kernel.org,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Odelu Kukatla <odelu.kukatla@....qualcomm.com>
Subject: Re: [PATCH v2 0/3] Add interconnect support for Glymur SoC
On 8/19/2025 7:22 PM, Krzysztof Kozlowski wrote:
> On 14/08/2025 16:54, Raviteja Laggyshetty wrote:
>> Add interconnect dt-bindings and driver support for
>> Qualcomm's next gen compute SoC - Glymur.
>> Device tree changes aren't part of this series and will be posted
>> separately after the official announcement of the Glymur SoC.
>
>
> No dependencies explained, so how maintainers can understand that they
> CANNOT apply this patch? :/
>
> Nice example of throwing the code over the wall, does not matter it does
> not even pass standard checks...
>
Sorry for the trouble, I have added dependencies using b4 prep
edit-deps option and I tried pulling few older changes using
shazam command and found that it automatically pulls the dependencies
from prerequisite-patch present in cover letter.
I made sure that dt_binding_checks are passing with dependency picked
into workspace. In future patches, I will make sure to explicitly point
out the dependency in the cover letter apart from adding it using b4
options.
Sorry for breaking the dt checker.
Thanks,
Raviteja
> Best regards,
> Krzysztof
Powered by blists - more mailing lists