From: Krzysztof Kozlowski <krzk@kernel.org>
To: Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mike Tipton <mike.tipton@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in Glymur SoC
Date: Tue, 19 Aug 2025 21:17:17 +0200 [thread overview]
Message-ID: <33d2ef0e-d5c3-4e42-a3c7-e285331f07ef@kernel.org> (raw)
In-Reply-To: <36974682-c8f1-4bcd-91f3-255c6332c0fe@kernel.org>
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
next prev parent reply other threads:[~2025-08-19 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 14:54 [PATCH v2 0/3] Add interconnect support for Glymur SoC Raviteja Laggyshetty
2025-08-14 14:54 ` [PATCH v2 1/3] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2025-08-19 13:31 ` Rob Herring
2025-08-19 13:46 ` Georgi Djakov
2025-08-19 16:03 ` Krzysztof Kozlowski
2025-08-19 18:02 ` Georgi Djakov
2025-08-19 19:17 ` Krzysztof Kozlowski [this message]
2025-08-19 18:35 ` Dmitry Baryshkov
2025-08-14 14:54 ` [PATCH v2 2/3] interconnect: qcom: icc-rpmh: increase MAX_PORTS to support four QoS ports Raviteja Laggyshetty
2025-08-16 12:43 ` Dmitry Baryshkov
2025-08-14 14:54 ` [PATCH v2 3/3] interconnect: qcom: add glymur interconnect provider driver Raviteja Laggyshetty
2025-08-16 12:43 ` Dmitry Baryshkov
2025-08-19 13:52 ` [PATCH v2 0/3] Add interconnect support for Glymur SoC Krzysztof Kozlowski
2025-08-20 6:06 ` Raviteja Laggyshetty
2025-08-20 6:28 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33d2ef0e-d5c3-4e42-a3c7-e285331f07ef@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike.tipton@oss.qualcomm.com \
--cc=odelu.kukatla@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).