[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC v3 00/13] linux: generalize sections, ranges and linker tables
- To: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
- Date: Tue, 9 Aug 2016 21:51:13 -0700
- Cc: One Thousand Gnomes <gnomes@xxxxxxxxxxxxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, realmz6@xxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, benh@xxxxxxxxxxxxxxxxxxx, ming.lei@xxxxxxxxxxxxx, heiko.carstens@xxxxxxxxxx, linux@xxxxxxxxxxxxxxxxxx, platform-driver-x86@xxxxxxxxxxxxxxx, paul.gortmaker@xxxxxxxxxxxxx, hpa@xxxxxxxxx, masami.hiramatsu.pt@xxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, sparclinux@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux@xxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, anil.s.keshavamurthy@xxxxxxxxx, fontana@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, catalin.marinas@xxxxxxx, dvhart@xxxxxxxxxxxxx, dwmw2@xxxxxxxxxxxxx, mhiramat@xxxxxxxxxx, rusty@xxxxxxxxxxxxxxx, keescook@xxxxxxxxxxxx, arnd@xxxxxxxx, linux-kbuild@xxxxxxxxxxxxxxx, will.deacon@xxxxxxx, pali.rohar@xxxxxxxxx, rostedt@xxxxxxxxxxx, christopher.denicolo@xxxxxxxx, jbaron@xxxxxxxxxx, ananth@xxxxxxxxxxxxxxxxxx, ciaran.farrell@xxxxxxxx, jpoimboe@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, andriy.shevchenko@xxxxxxxxxxxxxxx, mcb30@xxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, alan@xxxxxxxxxxxxxxx, jgross@xxxxxxxx, pebolle@xxxxxxxxxx, tony.luck@xxxxxxxxx, ananth@xxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, davem@xxxxxxxxxxxxx, ak@xxxxxxxxxxxxxxx, "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>, mmarek@xxxxxxxx, david.vrabel@xxxxxxxxxx, jkosina@xxxxxxx, bp@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, korea.drzix@xxxxxxxxx
- Delivery-date: Wed, 10 Aug 2016 04:51:31 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Aug 9, 2016 7:09 PM, "James Bottomley" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, 2016-08-09 at 15:24 +0100, One Thousand Gnomes wrote:
> > > table development go under copyleft-next, Rusty recently asked for
> > > code to go in prior to the license tag being added denoting this
> > > license as GPL-compatible [3] -- I had noted in the patch
> > > submission which annotated copyleft-next's compatibility to GPLv2
> > > that copyleft-next is the license of choice for ongoing kernel
> > > development on my end [4]. If this is objectionable I'm happy to
> > > change it to GPLv2 however I'd like a reason provided as I've gone
> > > through all possible channels to ensure this is kosher, including
> > > vetting by 3 attorneys now, 2 at SUSE.
> >
> > You don't need a new tag, you can use "GPL" or "GPL and additional
> > rights". In fact you don't want any other tag because when combined
> > with the kernel it is GPLv2 anyway because the only way the two are
> > fully compatible is for the kernel community to license the derived
> > work under the GPL.
>
> This is the module tag ... it says what licence the module is under,
> not the licence for the module combined with the kernel, which is
> always GPLv2 because the stricter licence rules.
Then why isn't "BSD" in the license_is_gpl_compatible list?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
