LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nadav Amit <namit@vmware.com>
Cc: "valdis.kletnieks@vt.edu" <valdis.kletnieks@vt.edu>,
Xavier Deguillard <xdeguillard@vmware.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 6/7] vmw_balloon: update copyright message
Date: Sat, 16 Jun 2018 10:03:52 +0200 [thread overview]
Message-ID: <20180616080352.GA20457@kroah.com> (raw)
In-Reply-To: <5151EA1B-D065-44D1-995C-47B791F574E1@vmware.com>
On Fri, Jun 15, 2018 at 08:38:57PM +0000, Nadav Amit wrote:
> at 1:35 PM, valdis.kletnieks@vt.edu wrote:
>
> > On Thu, 14 Jun 2018 05:33:46 -0000, Nadav Amit said:
> >
> >>>> In addition, updating the year and adding a license tag.
> >
> >>>> +// SPDX-License-Identifier: GPL-2.0
> >
> >>> You still have a lot of boiler-plate text in here that can be removed.
> >>> Please do so.
> >
> >> But what else do you want me to remove? This is a standard GPL license. If I
> >> am required to remove the GPL license, I will have to run checks to ensure
> >> it is appropriate.
> >
> > You mean the checks that you should have done when you stuck the SPDX
> > tag on the file?
> >
> > (Hint: Think of the SPDX tag as a '#include gplv2.license.blurb" :)
>
> I matched the SPDX to the license we have, tut I don’t know whether my
> company regards an SPDX tag as a sufficient means to protect copyrights,
> which allows to remove all the rest of the text.
Copyrights have nothing to do with SPDX lines, please don't get
copyrights and licenses confused, they are two totally different things.
Removing the license boilerplate and only using a SPDX line for the
license marking does not change the copyright of a file at all. And if
you use the correct SPDX line, it will not change the license of the
file at all either.
If your company's lawyers have any questions about this, I am glad to
discuss this with them and point them at the lawyers that created the
SPDX group.
But really, your company lawyers already know all about this, you should
not have any problems at all. If you are worried about this, please
contact your open source group and they will be glad to help out. I
have names if you want me to send them to you off-list :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-06-16 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:54 [PATCH v2 0/7] vmw_balloon: addressing bugs and issues Nadav Amit
2018-06-13 13:54 ` [PATCH v2 1/7] vmw_balloon: fix inflation of 64-bit GFNs Nadav Amit
2018-06-14 5:23 ` Greg Kroah-Hartman
2018-06-14 5:41 ` Nadav Amit
2018-06-14 5:50 ` Greg Kroah-Hartman
2018-06-14 5:56 ` Nadav Amit
2018-06-13 13:54 ` [PATCH v2 2/7] vmw_balloon: do not use 2MB without batching Nadav Amit
2018-06-13 13:54 ` [PATCH v2 3/7] vmw_balloon: VMCI_DOORBELL_SET does not check status Nadav Amit
2018-06-13 13:54 ` [PATCH v2 4/7] vmw_balloon: fix VMCI use when balloon built into kernel Nadav Amit
2018-06-13 13:54 ` [PATCH v2 5/7] vmw_balloon: remove inflation rate limiting Nadav Amit
2018-06-13 13:54 ` [PATCH v2 6/7] vmw_balloon: update copyright message Nadav Amit
2018-06-14 5:24 ` Greg Kroah-Hartman
2018-06-14 5:33 ` Nadav Amit
2018-06-14 5:48 ` Greg Kroah-Hartman
2018-06-15 20:35 ` valdis.kletnieks
2018-06-15 20:38 ` Nadav Amit
2018-06-16 8:03 ` Greg Kroah-Hartman [this message]
2018-06-13 13:54 ` [PATCH v2 7/7] vmw_balloon: update maintainers list Nadav Amit
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=20180616080352.GA20457@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.com \
--cc=valdis.kletnieks@vt.edu \
--cc=xdeguillard@vmware.com \
--subject='Re: [PATCH v2 6/7] vmw_balloon: update copyright message' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).