From: Chengci.Xu <chengci.xu@mediatek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: <iommu@lists.linux.dev>, <linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU
Date: Fri, 9 Sep 2022 15:39:14 +0800 [thread overview]
Message-ID: <f70232ad7365fbd8fb27a8658b9633897c7b18a4.camel@mediatek.com> (raw)
In-Reply-To: <87307ae4-a320-5880-1333-6ea700b61ca7@linaro.org>
On Fri, 2022-09-09 at 09:11 +0200, Krzysztof Kozlowski wrote:
> On 09/09/2022 05:20, Chengci.Xu wrote:
> > > > +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) */
> > >
> > > Why do you license it under BSD-3 clause?
> > >
> >
> > A mediatek internal wiki suggest me use "BSD-3-Clause" without
> > detial
> > reason. May be it is not suitable for this file.
> >
> > If you don't approve of this, I can change this license to "GPL-
> > 2.0-
> > only OR BSD-2-Clause", which is perferred by DT bindings file
> > according
> > to "submitting-patches.rst".
> >
> > Do you think "BSD-2-Clause" is OK? Or could you kindly share me
> > another
> > proper license?
>
> Please switch to "GPL-2.0-only OR BSD-2-Clause", which is preferred
> for
> bindings.
Thanks for your advice, we will use "GPL-2.0-only OR BSD-2-Clause".
Best regards,
Chengci Xu
>
>
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-09 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 12:54 [PATCH v2 0/3] MT8188 IOMMU SUPPORT Chengci.Xu
2022-08-31 12:55 ` [PATCH v2 1/3] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU Chengci.Xu
2022-09-08 10:49 ` Krzysztof Kozlowski
2022-09-09 3:20 ` Chengci.Xu
2022-09-09 7:11 ` Krzysztof Kozlowski
2022-09-09 7:39 ` Chengci.Xu [this message]
2022-08-31 12:55 ` [PATCH v2 2/3] iommu/mediatek: Add enable IOMMU SMC command for INFRA master Chengci.Xu
2022-09-02 9:00 ` AngeloGioacchino Del Regno
2022-09-08 7:46 ` Chengci.Xu
2022-09-07 3:37 ` Yong Wu
2022-09-08 10:03 ` Chengci.Xu
2022-08-31 12:55 ` [PATCH v2 3/3] iommu/mediatek: Add MT8188 IOMMU Support Chengci.Xu
2022-09-02 9:04 ` AngeloGioacchino Del Regno
2022-09-08 9:57 ` Chengci.Xu
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=f70232ad7365fbd8fb27a8658b9633897c7b18a4.camel@mediatek.com \
--to=chengci.xu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--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=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yong.wu@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;
as well as URLs for NNTP newsgroup(s).