From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: neil.armstrong@linaro.org, Abel Vesa <abel.vesa@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 03/10] arm64: dts: qcom: Add pm8010 pmic dtsi
Date: Mon, 21 Nov 2022 14:50:28 +0100 [thread overview]
Message-ID: <e0835b03-c409-ef0b-501b-176251bc1725@linaro.org> (raw)
In-Reply-To: <081732c9-5e8e-b68e-c2bd-20724ca1a5d5@linaro.org>
On 21/11/2022 14:29, neil.armstrong@linaro.org wrote:
>>>> Any reason why this is licensed BSD-3 clause? It's not a recommended
>>>> license (2 clause is). Same for other patches.
>>>
>>> Probably a bad copy-paste from other existing files.
>>>
>>> While checking, the majority of arch/arm64/boot/dts/qcom/pm*.dtsi uses BSD-3-Clause
>>> so it seems this was done for quite a while now.
>>
>> If it is derivative work (of upstrea, downstream), then you might have
>> to keep BSD-3. But if not, how about changing it to BSD-2?
>
> It's definitely a derivative work from upstream pm*.dtsi files with BSD-3-Clause
> licence.
OK.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-21 13:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 10:31 [PATCH 00/10] Add base device tree files for SM8550 Abel Vesa
2022-11-16 10:31 ` [PATCH 01/10] dt-bindings: arm: qcom: Document SM8550 SoC and boards Abel Vesa
2022-11-16 13:10 ` Krzysztof Kozlowski
2022-11-16 10:31 ` [PATCH 02/10] arm64: dts: qcom: Add base SM8550 dtsi Abel Vesa
2022-11-16 11:02 ` Konrad Dybcio
2022-11-16 11:28 ` Konrad Dybcio
2022-11-17 12:50 ` Krzysztof Kozlowski
2022-11-16 10:31 ` [PATCH 03/10] arm64: dts: qcom: Add pm8010 pmic dtsi Abel Vesa
2022-11-16 11:06 ` Konrad Dybcio
2022-11-17 12:51 ` Krzysztof Kozlowski
2022-11-18 14:58 ` Neil Armstrong
2022-11-18 14:59 ` Krzysztof Kozlowski
2022-11-21 13:29 ` neil.armstrong
2022-11-21 13:50 ` Krzysztof Kozlowski [this message]
2022-11-16 10:31 ` [PATCH 04/10] arm64: dts: qcom: Add PM8550 " Abel Vesa
2022-11-16 11:07 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 05/10] arm64: dts: qcom: Add PM8550b " Abel Vesa
2022-11-16 11:07 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 06/10] arm64: dts: qcom: Add PM8550ve " Abel Vesa
2022-11-16 11:07 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 07/10] arm64: dts: qcom: Add PM8550vs " Abel Vesa
2022-11-16 11:08 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 08/10] arm64: dts: qcom: Add PMK8550 " Abel Vesa
2022-11-16 11:09 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 09/10] arm64: dts: qcom: Add PMR735d " Abel Vesa
2022-11-16 11:09 ` Konrad Dybcio
2022-11-16 10:31 ` [PATCH 10/10] arm64: dts: qcom: Add base SM8550 MTP dts Abel Vesa
2022-11-16 11:14 ` Konrad Dybcio
2022-11-17 12:53 ` Krzysztof Kozlowski
2022-11-18 11:08 ` kernel test robot
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=e0835b03-c409-ef0b-501b-176251bc1725@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@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).