From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Rob Herring <robh@kernel.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Maxime Ripard <mripard@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mtd: Fix nand-controller.yaml license
Date: Mon, 26 Jun 2023 13:11:18 +0200 [thread overview]
Message-ID: <20230626131118.0f6fd166@windsurf> (raw)
In-Reply-To: <20230623210508.GA1096125-robh@kernel.org>
Hello Rob,
On Fri, 23 Jun 2023 15:05:08 -0600
Rob Herring <robh@kernel.org> wrote:
> Yes, we do want dual license, but things converted from txt bindings
> need those authors' permission as the txt bindings are all implicitly
> GPLv2. That didn't happen here, so we kept the default implicit license.
> Looks like this case is all Bootlin authors for significant parts of the
> original txt binding, so you should be good on that part (assuming your
> employer agrees). Maxime did the schema, so need his permission too.
>
> Note I have blanket permission on dual licensing from several companies
> for DT files. It would be nice to get the same from Bootlin.
I hereby allow the relicensing of all contributions from Bootlin
employees on Device Tree binding documents in the Linux kernel from
GPLv2 to GPLv2 or BSD-2-Clause.
Let me know if this statement is sufficient or if you need anything
more formal or specific.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Rob Herring <robh@kernel.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Maxime Ripard <mripard@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mtd: Fix nand-controller.yaml license
Date: Mon, 26 Jun 2023 13:11:18 +0200 [thread overview]
Message-ID: <20230626131118.0f6fd166@windsurf> (raw)
In-Reply-To: <20230623210508.GA1096125-robh@kernel.org>
Hello Rob,
On Fri, 23 Jun 2023 15:05:08 -0600
Rob Herring <robh@kernel.org> wrote:
> Yes, we do want dual license, but things converted from txt bindings
> need those authors' permission as the txt bindings are all implicitly
> GPLv2. That didn't happen here, so we kept the default implicit license.
> Looks like this case is all Bootlin authors for significant parts of the
> original txt binding, so you should be good on that part (assuming your
> employer agrees). Maxime did the schema, so need his permission too.
>
> Note I have blanket permission on dual licensing from several companies
> for DT files. It would be nice to get the same from Bootlin.
I hereby allow the relicensing of all contributions from Bootlin
employees on Device Tree binding documents in the Linux kernel from
GPLv2 to GPLv2 or BSD-2-Clause.
Let me know if this statement is sufficient or if you need anything
more formal or specific.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
next prev parent reply other threads:[~2023-06-26 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 21:24 [PATCH] dt-bindings: mtd: Fix nand-controller.yaml license Miquel Raynal
2023-06-22 21:24 ` Miquel Raynal
2023-06-23 21:05 ` Rob Herring
2023-06-23 21:05 ` Rob Herring
2023-06-26 11:11 ` Thomas Petazzoni [this message]
2023-06-26 11:11 ` Thomas Petazzoni
2023-06-26 11:16 ` Maxime Ripard
2023-06-26 11:16 ` Maxime Ripard
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=20230626131118.0f6fd166@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=mripard@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.