lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3cc79dc3-8514-44bd-a143-03e97fc65355@kernel.org>
Date: Wed, 20 Aug 2025 08:28:35 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@....qualcomm.com>,
 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 20/08/2025 08:06, Raviteja Laggyshetty wrote:
> 
> 
> 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 

Please wait for a minute and carefully think about that: did it make
sense? What exactly did you expect?

Interconnect maintainer will pull this patchset and the dependencies
(e.g. clock patches), yes? That's what you expected?

So what about the same patches in the clock tree?

> 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

This is not how you should create branches and your instruction how to
work on Glymur included that. :/


Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ