From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Slaby <jirislaby@gmail.com>,
linux-next@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: writable limits to -next
Date: Mon, 26 Oct 2009 01:35:11 +0100 [thread overview]
Message-ID: <m3eiorc7r4.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20091026094741.5a1d492c.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 26 Oct 2009 09:47:41 +1100")
Hi,
BTW you may want to check if the current wording is correct:
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> You will need to ensure that the patches/commits in your tree/series have
> been:
> * submitted under GPL v2 (or later) and include the Contributor's
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It's not ok to submit under e.g. GPL v3 only, I'd suggest "under GPL v2
and optionally other licence(s)" or something like that.
For example code under BSD-style licence (in addition to GPLv2) is
present in Linux, though I think any additional licence (the "later" as
in "GPL v2 or later", GPL v3, MS EULA etc.) is acceptable as long as it
is really additional, i.e., if one can ignore it and "use" GPLv2
exclusively.
IANAL of course.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-10-26 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 17:08 Adding to linux-next? Gregory Haskins
2009-10-06 11:57 ` Stephen Rothwell
2009-10-23 8:36 ` writable limits to -next [was: Adding to linux-next?] Jiri Slaby
2009-10-25 22:47 ` Stephen Rothwell
2009-10-25 22:55 ` Stephen Rothwell
2009-10-25 23:37 ` Jiri Slaby
2009-10-26 0:35 ` Krzysztof Halasa [this message]
2009-10-26 1:04 ` writable limits to -next Stephen Rothwell
2009-10-26 13:04 ` Krzysztof Halasa
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=m3eiorc7r4.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=jirislaby@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=sfr@canb.auug.org.au \
/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).