[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33d2ef0e-d5c3-4e42-a3c7-e285331f07ef@kernel.org>
Date: Tue, 19 Aug 2025 21:17:17 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Georgi Djakov <djakov@...nel.org>, Rob Herring <robh@...nel.org>,
Raviteja Laggyshetty <raviteja.laggyshetty@....qualcomm.com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
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 1/3] dt-bindings: interconnect: document the RPMh
Network-On-Chip interconnect in Glymur SoC
On 19/08/2025 20:02, Georgi Djakov wrote:
>>>> this until the dependency is there.
>>>
>>> Thanks! And now i see why my script didn't catch this... now fixed and
>>> patch dropped.
>>
>> What are you using to apply patches? Because b4 would pull all
>> dependencies, which would brake your branch as well, but at least you
>> would see something odd happening here.
>
> I am using b4, but in cherry-pick mode, so i just pipe the current email to
Ah, that's the answer. Cherry-pick does not pick up dependencies, so you
would not see weird commits tagging along :)
> it. And i also noticed the prerequisite-change-id lines and the dependency
> on gcc, but my local scripts (that do all kinds of checks) passed, because
> of a bug that didn't properly log the dt_binding_check error, so i thought
> the dependency is there. I recently modified it to run with not just the
Best regards,
Krzysztof
Powered by blists - more mailing lists