From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, robh+dt@kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
chun-jie.chen@mediatek.com, weiyi.lu@mediatek.com,
mbrugger@suse.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com,
nfraprado@collabora.com
Subject: Re: [PATCH 1/2] dt-bindings: power: Add MediaTek Helio X10 MT6795 power domains
Date: Tue, 3 May 2022 14:58:31 +0200 [thread overview]
Message-ID: <64129cb4-f33f-6017-4923-63f67f7067fa@collabora.com> (raw)
In-Reply-To: <d371fff5-0d45-b827-2696-3862b3c5fd59@linaro.org>
Il 03/05/22 14:57, Krzysztof Kozlowski ha scritto:
> On 03/05/2022 14:43, AngeloGioacchino Del Regno wrote:
>>>
>>> If it is not a derivative work, should be GPL-2.0 OR BSD
>>>
>>
>> On that, I agree with you, fully.
>>
>> Though, all of the mt(xxxx)-power.h headers provide this license tag and I
>> wanted to follow that to give the same.
>>
>> Should I change it to (GPL-2.0-only OR BSD-2-Clause)?
>
> Yes, please, for this one.
>
> For the other bindings - you would need acks from people involved.
>
I'm glad to read this. I'll change it in the next version. Thank you!
next prev parent reply other threads:[~2022-05-03 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 10:54 [PATCH 0/2] MediaTek Helio X10 MT6795 - power domains AngeloGioacchino Del Regno
2022-05-03 10:54 ` [PATCH 1/2] dt-bindings: power: Add MediaTek Helio X10 MT6795 " AngeloGioacchino Del Regno
2022-05-03 12:38 ` Krzysztof Kozlowski
2022-05-03 12:43 ` AngeloGioacchino Del Regno
2022-05-03 12:57 ` Krzysztof Kozlowski
2022-05-03 12:58 ` AngeloGioacchino Del Regno [this message]
2022-05-03 10:54 ` [PATCH 2/2] soc: mediatek: pm-domains: Add support for Helio X10 MT6795 AngeloGioacchino Del Regno
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=64129cb4-f33f-6017-4923-63f67f7067fa@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mbrugger@suse.com \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=weiyi.lu@mediatek.com \
/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