| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150512224011.GA8747@gandalf.middle.earth.net> Date: Tue, 12 May 2015 18:40:11 -0400 From: "George G. Davis" <ggdavisiv@...il.com> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org Subject: Re: lustre_dlm_flags.h GPLv3 license clarification Hello Greg, On Tue, May 12, 2015 at 03:31:17PM -0700, Greg Kroah-Hartman wrote: > On Tue, May 12, 2015 at 06:05:24PM -0400, George G. Davis wrote: > > Greetings, > > > > 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]? > > Please resend this to the owners of this file (hint, get_maintainers.pl > will get you the list...) Oops, I had an old v3.14.41 based version of get_maintainers.pl checked out. I'll resend after using the correct version of get_maintainers.pl. Thanks! -- Regards, George > > thanks, > > greg k-h -- 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