From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Alejandro Vazquez <avazquez.dev@gmail.com>,
ptxdist@pengutronix.de, Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v3] tf-a: new package for ARM trusted firmware A
Date: Thu, 27 Feb 2020 11:56:04 +0100 [thread overview]
Message-ID: <45f693d3-9219-0626-a3e0-58b83347908c@pengutronix.de> (raw)
In-Reply-To: <20200227094731.vmlunmba7qucc7lw@pengutronix.de>
Hi,
On 2/27/20 10:47 AM, Roland Hieber wrote:
> On Tue, Feb 25, 2020 at 10:44:18AM +0100, Ahmad Fatoum wrote:
>> When patching some parts of the code, the patches need to be dually licensed,
>
> I don't understand why this is the case, even if docs/license.rst says
> so. If libfdt authors and STM allows us to choose between BSD or
> GPL-2.0, we can choose to distribute our patches under any one of those.
> (And if we choose BSD, which also TF-A did, we don't even need to
> license our contributions as BSD since BSD has no copyleft). Sure, our
> patches probably won't be accepted upstream by libfdt or STM under only
> those licenses, but that's another problem.
Makes sense. Thanks for the clarification.
> In any way I think it's best to resolve this by keeping the original
> disjunctive license statements:
>
> BSD-3-Clause AND BSD-2-Clause # main license and FreeBSD libc
> AND (GPL-2.0-or-later OR BSD-2-Clause) # libfdt
> AND (NCSA OR MIT) # LLVM compiler-rt
> AND Zlib # zlib
> AND (GPL-2.0-or-later OR BSD-3-Clause) # STM platform code>
> This way it is clear that we can choose between GPL and BSD for parts of
> the code, even if the most reasonable outcome of the calculation of all
> license terms is effectively BSD-3-Clause.
Will do in v4.
Thanks for your input,
Ahmad
>
> - Roland
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-02-27 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 10:42 Ahmad Fatoum
2020-02-25 7:31 ` Michael Tretter
2020-02-25 9:20 ` Philipp Zabel
2020-02-25 9:44 ` Ahmad Fatoum
2020-02-27 9:47 ` Roland Hieber
2020-02-27 10:56 ` Ahmad Fatoum [this message]
2020-02-25 9:44 ` Michael Olbrich
2020-02-25 10:35 ` Ahmad Fatoum
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=45f693d3-9219-0626-a3e0-58b83347908c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=avazquez.dev@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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