From: Etienne CARRIERE - foss <etienne.carriere@foss.st.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Lee Jones <lee@kernel.org>,
Pascal PAILLET-LME <p.paillet@st.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2] dt-bindings: mfd: dual licensing for st,stpmic1 bindings
Date: Mon, 17 Jun 2024 09:21:13 +0000 [thread overview]
Message-ID: <15b20cdd8b9148559352fdb2f02e4e53@foss.st.com> (raw)
In-Reply-To: <20240617092016.2958046-1-etienne.carriere@foss.st.com>
Hello Conor,
>
> From: Conor Dooley <conor@kernel.org>
> Sent: Saturday, June 15, 2024 2:14 PM
>
> On Fri, Jun 14, 2024 at 05:33:46PM +0200, Etienne Carriere wrote:
> > Change include/dt-bindings/mfd/st,stpmic1.h license model from GPLv2.0
> > only to dual GPLv2.0 or BSD-3-Clause. I have every legitimacy to request
> > this change on behalf of STMicroelectronics. This change clarifies that
> > this DT binding header file can be shared with software components as
> > bootloaders and OSes that are not published under GPLv2 terms.
> >
> > In CC are all the contributors to this header file.
> >
> > Cc: Pascal Paillet <p.paillet@st.com>
> > Cc: Lee Jones <lee.jones@linaro.org>
> > Cc: Rob Herring <robh@kernel.org>
> > Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
> > ---
> > include/dt-bindings/mfd/st,stpmic1.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/dt-bindings/mfd/st,stpmic1.h b/include/dt-bindings/mfd/st,stpmic1.h
> > index 321cd08797d9..957c48300cd4 100644
> > --- a/include/dt-bindings/mfd/st,stpmic1.h
> > +++ b/include/dt-bindings/mfd/st,stpmic1.h
> > @@ -1,4 +1,4 @@
> > -/* SPDX-License-Identifier: GPL-2.0 */
> > +/* SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause */
>
> The usual dual license for bindings is BSD-2-Clause, was there a
> specific request for the 3 version?
My mistake. Thanks for spotting that.
I have my company agreement for the 2 dual models: "OR BSD-2-Clause" and "OR BSD-3-Clause".
We expect to conform to DT bindings preferred licensing model. Indeed the kernel documentation explicitly mention "GPL-2.0-only OR BSD-2-Clause".
We prefer to conform with it. I'll update my patch.
By the way, I'll fix Lee Jones e-mail address that is deprecated.
BR,
Etienne
>
> > /*
> > * Copyright (C) STMicroelectronics 2018 - All Rights Reserved
> > * Author: Philippe Peurichard <philippe.peurichard@st.com>,
> > --
> > 2.25.1
> >
>
next prev parent reply other threads:[~2024-06-17 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 9:20 [PATCH v2] dt-bindings: mfd: dual licensing for st,stpmic1 bindings Etienne Carriere
2024-06-17 9:21 ` Etienne CARRIERE - foss [this message]
2024-06-17 15:13 ` Conor Dooley
2024-06-17 15:15 ` Conor Dooley
2024-06-17 15:15 ` Conor Dooley
[not found] ` <VE1PR10MB3407EE2C8715D390E286BDB385CE2@VE1PR10MB3407.EURPRD10.PROD.OUTLOOK.COM>
2024-06-18 8:00 ` Pascal PAILLET-LME
2024-06-24 16:37 ` Rob Herring
2024-06-26 15:53 ` (subset) " Lee Jones
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=15b20cdd8b9148559352fdb2f02e4e53@foss.st.com \
--to=etienne.carriere@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=p.paillet@st.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).