All of lore.kernel.org
 help / color / mirror / Atom feed
From: "George G. Davis" <ggdavisiv@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: lustre_dlm_flags.h GPLv3 license clarification
Date: Tue, 12 May 2015 18:40:11 -0400	[thread overview]
Message-ID: <20150512224011.GA8747@gandalf.middle.earth.net> (raw)
In-Reply-To: <20150512223117.GA15915@kroah.com>

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

  reply	other threads:[~2015-05-12 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 22:05 lustre_dlm_flags.h GPLv3 license clarification George G. Davis
2015-05-12 22:31 ` Greg Kroah-Hartman
2015-05-12 22:40   ` George G. Davis [this message]
2015-05-12 22:43 George G. Davis
2015-05-13  1:53 ` Drokin, Oleg
2015-05-13 13:09   ` 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=20150512224011.GA8747@gandalf.middle.earth.net \
    --to=ggdavisiv@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.