[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150513130954.GA10638@gandalf.middle.earth.net>
Date: Wed, 13 May 2015 09:09:54 -0400
From: "George G. Davis" <ggdavisiv@...il.com>
To: "Drokin, Oleg" <oleg.drokin@...el.com>
Cc: "<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"<devel@...verdev.osuosl.org>" <devel@...verdev.osuosl.org>,
"<HPDD-discuss@...ts.01.org>" <HPDD-discuss@...ts.01.org>
Subject: Re: lustre_dlm_flags.h GPLv3 license clarification
Hello Oleg,
On Wed, May 13, 2015 at 01:53:35AM +0000, Drokin, Oleg wrote:
> Hello!
>
> On May 12, 2015, at 6:43 PM, George G. Davis wrote:
>
> > Greetings,
> >
> > Resending this using the correct version of get_maintainers.pl.
> >
> > As recommended in the thread "SPDX-License-Identifier” [1], I would like to followup with the
> > maintainers of the file drivers/staging/lustre/lustre/include/lustre_dlm_flags.h regarding the GPLv3
> > license statement contained in that file [2]. Is there an GPLv3 exception clause which can be applied
> > for this file similar to the bison exception clause or is this file licensed only under GPLv3 only in which
> > case it would appear to be incompatible with the Linux kernel license [3]?
>
> Duh.
> It appears that the file was automatically generated in the lustre tree with autogen and somebody forgot to
> specify gpl version, so it defaulted to v3:
> [= (gpl "lustre" " * ") =]
>
>
> Thanks.
>
> I think we'll be able to change that to gplv2 easily (to match the rest of Lustre).
Awesome, thanks! Looking forward to the patch. : )
--
Regards,
George
>
> Bye,
> Oleg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists