devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Djakov <djakov@kernel.org>
To: 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 16:46:13 +0300	[thread overview]
Message-ID: <363db534-92a2-4108-8a41-8e07ec22513d@kernel.org> (raw)
In-Reply-To: <CAL_JsqL+C1VueQjrKra8fNTd-2k=gkoy-jA9uuQOhuyRMbQroQ@mail.gmail.com>

On 8/19/25 4:31 PM, Rob Herring wrote:
> On Thu, Aug 14, 2025 at 9:54 AM Raviteja Laggyshetty
> <raviteja.laggyshetty@oss.qualcomm.com> wrote:
>>
>> Document the RPMh Network-On-Chip Interconnect in Glymur platform.
>>
>> Co-developed-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
>> Signed-off-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>> ---
>>   .../bindings/interconnect/qcom,glymur-rpmh.yaml    | 172 +++++++++++++++++
>>   .../dt-bindings/interconnect/qcom,glymur-rpmh.h    | 205 +++++++++++++++++++++
>>   2 files changed, 377 insertions(+)
> 
> This is breaking linux-next "make dt_binding_check". Looks like the
> clock header dependency in the example is not applied. Please drop
> this until the dependency is there.

Thanks! And now i see why my script didn't catch this... now fixed and
patch dropped.

BR,
Georgi

  reply	other threads:[~2025-08-19 13:46 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 [this message]
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

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=363db534-92a2-4108-8a41-8e07ec22513d@kernel.org \
    --to=djakov@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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).