From: Etienne Carriere <etienne.carriere@linaro.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, "Stephen Warren" <swarren@nvidia.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Laxman Dewangan" <ldewangan@nvidia.com>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Nuno Sá" <nuno.sa@analog.com>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v2] dt-binding: gpio: publish binding IDs under dual license
Date: Mon, 5 Sep 2022 16:52:08 +0200 [thread overview]
Message-ID: <CAN5uoS8v0Hq0U4-4LUvrcQRATTpTa7unH8_h_xTX4Rdxn12tRQ@mail.gmail.com> (raw)
In-Reply-To: <20220905085929.38c737fc@windsurf>
Hi Thomas,
On Mon, 5 Sept 2022 at 08:59, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Thu, 1 Sep 2022 18:36:36 +0200
> Etienne Carriere <etienne.carriere@linaro.org> wrote:
>
> > Changes gpio.h DT binding header file to be published under GPLv2 or
> > BSD-3-Clause license terms. This change allows these GPIO generic
>
> You're actually changing to BSD-2-Clause. Your v1 changed to
> BSD-3-Clause, but following feedback, you change the SPDX code to
> BSD-2-Clause but forgot to update the commit log.
Right, my apologies.
I'll fix in v3.
Br,
etienne
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
prev parent reply other threads:[~2022-09-05 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 16:36 [PATCH v2] dt-binding: gpio: publish binding IDs under dual license Etienne Carriere
2022-09-05 6:37 ` Krzysztof Kozlowski
2022-09-05 6:59 ` Thomas Petazzoni
2022-09-05 14:52 ` Etienne Carriere [this message]
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=CAN5uoS8v0Hq0U4-4LUvrcQRATTpTa7unH8_h_xTX4Rdxn12tRQ@mail.gmail.com \
--to=etienne.carriere@linaro.org \
--cc=andrew@aj.id.au \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.com \
--cc=thomas.petazzoni@bootlin.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).