From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
djakov@kernel.org, lumag@kernel.org, a39.skl@gmail.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
quic_rjendra@quicinc.com, raviteja.laggyshetty@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 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in Glymur SoC
Date: Thu, 31 Jul 2025 17:06:56 +0200 [thread overview]
Message-ID: <e8ac306d-7bff-415c-a290-a579109f9e29@kernel.org> (raw)
In-Reply-To: <20250716151535.4054172-2-pankaj.patil@oss.qualcomm.com>
On 16/07/2025 17:15, Pankaj Patil wrote:
> diff --git a/include/dt-bindings/interconnect/qcom,glymur-rpmh.h b/include/dt-bindings/interconnect/qcom,glymur-rpmh.h
> new file mode 100644
> index 000000000000..6993a686da55
> --- /dev/null
> +++ b/include/dt-bindings/interconnect/qcom,glymur-rpmh.h
> @@ -0,0 +1,205 @@
> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> +/*
> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
Please use copyright format as requested by GPL (see GPL FAQ how this
can be written).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-31 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 15:15 [PATCH 0/2] Add interconnect support for Glymur SoC Pankaj Patil
2025-07-16 15:15 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Pankaj Patil
2025-07-20 23:14 ` Rob Herring (Arm)
2025-07-31 15:06 ` Krzysztof Kozlowski [this message]
2025-07-16 15:15 ` [PATCH 2/2] interconnect: qcom: add glymur interconnect provider driver Pankaj Patil
2025-07-16 15:28 ` Dmitry Baryshkov
2025-07-20 13:19 ` Raviteja Laggyshetty
2025-07-20 15:02 ` Georgi Djakov
2025-07-20 15:10 ` Raviteja Laggyshetty
2025-07-17 20:33 ` Konrad Dybcio
2025-07-20 13:34 ` Raviteja Laggyshetty
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=e8ac306d-7bff-415c-a290-a579109f9e29@kernel.org \
--to=krzk@kernel.org \
--cc=a39.skl@gmail.com \
--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=lumag@kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=quic_rjendra@quicinc.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).