From: "George G. Davis" <ggdavisiv@gmail.com>
To: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, Oleg Drokin <oleg.drokin@intel.com>,
HPDD-discuss@ml01.01.org
Cc: "Davis George G." <ggdavisiv@gmail.com>
Subject: lustre_dlm_flags.h GPLv3 license clarification
Date: Tue, 12 May 2015 18:43:39 -0400 [thread overview]
Message-ID: <20150512224339.GB8747@gandalf.middle.earth.net> (raw)
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]?
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
next reply other threads:[~2015-05-12 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 22:43 George G. Davis [this message]
2015-05-13 1:53 ` lustre_dlm_flags.h GPLv3 license clarification Drokin, Oleg
2015-05-13 13:09 ` George G. Davis
-- strict thread matches above, loose matches on Subject: below --
2015-05-12 22:05 George G. Davis
2015-05-12 22:31 ` Greg Kroah-Hartman
2015-05-12 22:40 ` George G. Davis
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=20150512224339.GB8747@gandalf.middle.earth.net \
--to=ggdavisiv@gmail.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.