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>,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>,
Mike Tipton <mike.tipton@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add interconnect support for Kaanapali SoC
Date: Thu, 23 Oct 2025 08:22:13 +0200 [thread overview]
Message-ID: <63fc8add-356a-44fe-b5d5-9ef7bda04d76@kernel.org> (raw)
In-Reply-To: <20251023-knp-interconnect-v1-0-df13182aceac@oss.qualcomm.com>
On 23/10/2025 06:39, Raviteja Laggyshetty wrote:
> Add interconnect dt-bindings and driver support for Qualcomm Kaanapali SoC.
>
> bindings file depends on Kaanapali gcc patch header file:
> https://lore.kernel.org/all/20250924-knp-clk-v1-0-29b02b818782@oss.qualcomm.com/
They cannot. We told about this multiple times.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-23 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 4:39 [PATCH 0/2] Add interconnect support for Kaanapali SoC Raviteja Laggyshetty
2025-10-23 4:39 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2025-10-23 6:23 ` Krzysztof Kozlowski
2025-10-28 3:02 ` Aiqun(Maria) Yu
2025-10-23 4:39 ` [PATCH 2/2] interconnect: qcom: add Kaanapali interconnect provider driver Raviteja Laggyshetty
2025-10-23 14:10 ` Dmitry Baryshkov
2025-10-23 6:22 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-24 23:02 [PATCH 0/2] Add interconnect support for Kaanapali SoC Jingyi Wang
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=63fc8add-356a-44fe-b5d5-9ef7bda04d76@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).