From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts
Date: Tue, 2 Sep 2014 14:51:16 +0200 [thread overview]
Message-ID: <20140902125116.GW15297@lukather> (raw)
In-Reply-To: <5405B986.2080407@redhat.com>
On Tue, Sep 02, 2014 at 02:35:18PM +0200, Hans de Goede wrote:
> > So I guess like Chen-Yu suggested that we should change the license of
> > the DTSI first, and then the DTS. Otherwise, it wouldn't work very
> > well, I guess you can't really relicense a GPL-only file.
>
> IANAL, but mixing MIT (which I suggest use as the other license) and GPL
> files in one binary (the generated dtb file) is fine AFAIK, this happens
> all the time. The resulting binary is simple GPL licensed. So it would
> make sense to start with dual licensing new boards right away even before
> the dtsi has been relicensed. It won't make any practical difference
> until the dtsi is relicensed, but it means less work later on.
So you're allowed to licence derivative work of a GPL-licenced file
under both the GPL and another licence?
And as far as MIT vs BSD is concerned, I don't really have an
opinion. Arnd? Russell?
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140902/b995c0b1/attachment.sig>
next prev parent reply other threads:[~2014-09-02 12:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:20 Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts Karsten Merker
2014-08-03 13:04 ` Maxime Ripard
2014-08-03 17:59 ` Arnd Bergmann
2014-08-04 19:25 ` Maxime Ripard
2014-08-04 21:23 ` Russell King - ARM Linux
2014-08-05 8:06 ` Arnd Bergmann
2014-08-07 13:20 ` Maxime Ripard
2014-09-02 10:22 ` Maxime Ripard
2014-09-02 10:40 ` Russell King - ARM Linux
2014-09-02 11:54 ` Chen-Yu Tsai
2014-09-02 12:27 ` Maxime Ripard
2014-09-02 12:35 ` Hans de Goede
2014-09-02 12:51 ` Maxime Ripard [this message]
2014-09-02 13:02 ` Arnd Bergmann
2014-09-02 13:37 ` Russell King - ARM Linux
2014-09-02 16:52 ` Russell King - ARM Linux
2014-09-02 14:42 ` Hans de Goede
2014-09-02 15:18 ` Maxime Ripard
2014-09-02 16:24 ` Russell King - ARM Linux
2014-08-05 8:01 ` Hans de Goede
2014-08-05 8:02 ` Hans de Goede
2014-08-03 20:41 ` Russell King - ARM Linux
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=20140902125116.GW15297@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).