All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Straube <straube.linux@gmail.com>
Cc: devel@driverdev.osuosl.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Which SPDX Identifier for files without explicit GPL version
Date: Sun, 28 Oct 2018 11:27:28 +0000	[thread overview]
Message-ID: <20181028112728.GD8826@kroah.com> (raw)
In-Reply-To: <406c69c1-43fd-f821-b74b-a1399ed636e9@gmail.com>

On Sun, Oct 28, 2018 at 11:04:06AM +0100, Michael Straube wrote:
> Hi,
> 
> which GPL version should be used in SPDX Identifiers for files that
> are GPL licensed but do not mention any version? It is not clear to
> me after reading license-rules.rst.
> 
> For example:
> 
> /******************************************************************************
>  * Copyright(c) 2008 - 2010 Realtek Corporation. All rights reserved.
>  *
>  * This program is distributed in the hope that it will be useful, but WITHOUT
>  * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
>  * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
>  * more details.
>  *
>  * The full GNU General Public License is included in this distribution in the
>  * file called LICENSE.

Perhaps look up what version of the GPL that was originally contained in
the tarball that this driver was bundled with?  I think that should be
on their website somewhere...

If not, it's v1, not a good thing, but all we have to go on.  Also, try
emailing:

>  * Contact Information:
>  * wlanfae <wlanfae@realtek.com>

That address :)

thanks,

greg k-h

  reply	other threads:[~2018-10-28 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 10:04 Which SPDX Identifier for files without explicit GPL version Michael Straube
2018-10-28 11:27 ` Greg Kroah-Hartman [this message]
2018-10-28 13:22   ` Michael Straube
2018-10-28 14:13     ` Greg Kroah-Hartman
2018-10-28 19:58       ` Michael Straube

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=20181028112728.GD8826@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=straube.linux@gmail.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.