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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <FE5CD806-B7D1-4795-9304-3A14AFD9C032@gmail.com>
Date:	Tue, 12 May 2015 18:05:24 -0400
From:	"George G. Davis" <ggdavisiv@...il.com>
To:	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org
Cc:	"Davis George G." <ggdavisiv@...il.com>
Subject: lustre_dlm_flags.h GPLv3 license clarification

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]?

TIA!

—
Regards,
George

[1] https://lkml.org/lkml/2015/2/5/65
[2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h#n9
[3] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/COPYING--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ