From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Li Yang <leoli@freescale.com>
Cc: Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Sharma Bhupesh <bhupesh.sharma@freescale.com>,
Stuart Yoder <stuart.yoder@freescale.com>,
Peter Newton <Peter.Newton@freescale.com>
Subject: Re: License for ARM device tree file
Date: Mon, 28 Sep 2015 21:26:08 +0100 [thread overview]
Message-ID: <20150928202607.GF21513@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CADRPPNQniPRmLq4WmSPU818=PafUV99djC9JveajMVdxARz0KA@mail.gmail.com>
On Mon, Sep 28, 2015 at 03:19:05PM -0500, Li Yang wrote:
> On Mon, Sep 28, 2015 at 2:29 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > However, we can't dictate to people what license they wish to submit
> > their work under; though, we can make the decision whether to accept
> > it under the license terms or not.
>
> But I'm wondering if we submit a device tree patch using other GPL
> compatible permissive license(like GPL/3-clause-BSD dual license)
> which doesn't include any other device tree files, will it still be
> acceptable or not?
I don't see why it wouldn't be acceptable. The only thing that matters
for Linux itself is that it's GPL v2 compatible since the kernel is a
GPL v2 project.
> > I think the problem will come if we try to mix a file that's licensed
> > one way, which includes files licensed under a different set of
> > licenses... if you want to use a file licensed under BSD 3-clause but
> > don't want to agree to the GPL license (so you're only bound by the
> > BSD 3-clause license) and that file includes some GPL/X11 licensed
> > files, then what?
>
> Permissive licenses like X11 and BSD 3-clause should be compatible
> with each other right?
My point above is that you'd have to accept both X11 and BSD 3-clause
in that situation, if you wanted to reject GPL. I don't wish to get
into a discussion whether X11 and BSD 3-clause are mutually compatible
with each other, that's lawyer territory. :)
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-09-28 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 19:14 Li Leo
2015-09-28 19:29 ` Russell King - ARM Linux
2015-09-28 20:19 ` Li Yang
2015-09-28 20:26 ` Russell King - ARM Linux [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=20150928202607.GF21513@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Peter.Newton@freescale.com \
--cc=arnd@arndb.de \
--cc=bhupesh.sharma@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=leoli@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=stuart.yoder@freescale.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
all inboxes | Powered by JetHome®