From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: 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 0/3] Add interconnect support for Glymur SoC
Date: Wed, 20 Aug 2025 08:28:35 +0200 [thread overview]
Message-ID: <3cc79dc3-8514-44bd-a143-03e97fc65355@kernel.org> (raw)
In-Reply-To: <73921d66-8258-4f82-95a8-f4e9fe8acc8e@oss.qualcomm.com>
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
prev parent reply other threads:[~2025-08-20 6:28 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
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 [this message]
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=3cc79dc3-8514-44bd-a143-03e97fc65355@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).