From: Rob Herring <robh@kernel.org>
To: Etienne Carriere <etienne.carriere@foss.st.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lee Jones <lee@kernel.org>, Pascal Paillet <p.paillet@st.com>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2] dt-bindings: mfd: dual licensing for st,stpmic1 bindings
Date: Mon, 24 Jun 2024 10:37:02 -0600 [thread overview]
Message-ID: <20240624163702.GA4048689-robh@kernel.org> (raw)
In-Reply-To: <20240617092016.2958046-1-etienne.carriere@foss.st.com>
On Mon, Jun 17, 2024 at 11:20:16AM +0200, Etienne Carriere wrote:
> Change include/dt-bindings/mfd/st,stpmic1.h license model from GPLv2.0
> only to dual GPLv2.0 or BSD-2-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@kernel.org>
My copy comes from b4, and looks like it fixes old addresses. Neat.
> Cc: Rob Herring <robh@kernel.org>
The file only shows contributions from Pascal, so you don't need any
acks for license change. For the change itself:
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-06-24 16:37 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
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 [this message]
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=20240624163702.GA4048689-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@foss.st.com \
--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 \
/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).