From: Rohit Agarwal <quic_rohiagar@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<djakov@kernel.org>, <robh+dt@kernel.org>, <krzk+dt@kernel.org>
Cc: <manivannan.sadhasivam@linaro.org>,
<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: Add Qualcomm SDX65 DT bindings
Date: Wed, 13 Apr 2022 11:59:58 +0530 [thread overview]
Message-ID: <99e49c61-4a6a-69c6-810c-581ee0ce5008@quicinc.com> (raw)
In-Reply-To: <7e1e6c10-c02a-c8da-44c0-ba3abef1950e@linaro.org>
On 4/12/2022 2:52 PM, Krzysztof Kozlowski wrote:
> On 12/04/2022 07:07, Rohit Agarwal wrote:
>> Add interconnect IDs for Qualcomm SDX65 platform.
>>
>> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
> (...)
>
>> diff --git a/include/dt-bindings/interconnect/qcom,sdx65.h b/include/dt-bindings/interconnect/qcom,sdx65.h
>> new file mode 100644
>> index 0000000..8d02c79
>> --- /dev/null
>> +++ b/include/dt-bindings/interconnect/qcom,sdx65.h
>> @@ -0,0 +1,67 @@
>> +/* SPDX-License-Identifier: GPL-2.0-only */
> Is it possible to license it the same as bindings (GPL-2.0 OR BSD-2-Clause)?
The qcom related code are marked as GPL 2.0 license
Thanks,
Rohit.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-04-13 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 5:07 [PATCH 0/2] Add interconnect driver for SDX65 Rohit Agarwal
2022-04-12 5:07 ` [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm SDX65 DT bindings Rohit Agarwal
2022-04-12 9:22 ` Krzysztof Kozlowski
2022-04-13 6:29 ` Rohit Agarwal [this message]
2022-04-13 6:33 ` Krzysztof Kozlowski
2022-04-13 12:14 ` Rohit Agarwal
2022-04-13 12:21 ` Krzysztof Kozlowski
2022-04-13 12:24 ` Rohit Agarwal
2022-04-12 5:07 ` [PATCH 2/2] interconnect: qcom: Add SDX65 interconnect provider driver Rohit Agarwal
2022-04-12 11:16 ` 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=99e49c61-4a6a-69c6-810c-581ee0ce5008@quicinc.com \
--to=quic_rohiagar@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®