From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] USB: add SPDX identifiers to all files in drivers/usb/
Date: Fri, 20 Oct 2017 18:49:30 +0100 [thread overview]
Message-ID: <20171020184930.6b8815a5@alans-desktop> (raw)
In-Reply-To: <20171019091046.GA5712@kroah.com>
> But all that matters is the tag is there for tools to be able to extract
> it properly. And if we have that, it doesn't matter what the comment
> "style" would be, so might as well make it look "nicer".
>
> And, to take it to the next conclusion, if we have the SPDX identifier,
> we can get rid of the "boilerplate" GPL license crap as well, right?
An SPDX tag may not form a valid warranty disclaimer in many parts of
the world while the header with correct document text in capitals does.
So yes you can remove it, but since it used to have a disclaimer and
you (aka Linux Foundation) potentially removed it you might want to have a
little chat with their laywers about whether you risk assuming any
liability as a result 8)
I also don't think it would be appropriate to remove warranty disclaimers
from third party material without the owners permission (or some surety
from lawyers).
Alan
next prev parent reply other threads:[~2017-10-20 17:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 8:38 [PATCH] USB: add SPDX identifiers to all files in drivers/usb/ Greg Kroah-Hartman
2017-10-19 8:49 ` Geert Uytterhoeven
2017-10-19 8:52 ` Greg Kroah-Hartman
2017-10-19 9:10 ` Geert Uytterhoeven
2017-10-19 9:15 ` Thomas Gleixner
2017-10-19 9:27 ` Felipe Balbi
2017-10-19 8:50 ` Thomas Gleixner
2017-10-19 8:57 ` Greg Kroah-Hartman
2017-10-19 8:59 ` Greg Kroah-Hartman
2017-10-19 9:01 ` Thomas Gleixner
2017-10-19 9:10 ` Greg Kroah-Hartman
2017-10-19 10:55 ` Philippe Ombredanne
2017-10-20 17:49 ` Alan Cox [this message]
2017-10-21 7:46 ` Greg Kroah-Hartman
2017-10-20 15:26 ` Rob Herring
2017-10-21 7:48 ` Greg Kroah-Hartman
2017-10-24 10:36 ` Philippe Ombredanne
2017-11-03 10:28 ` [PATCH v2] USB: add SPDX identifiers to all remaining " Greg Kroah-Hartman
2017-11-03 10:29 ` Greg Kroah-Hartman
2017-11-03 10:50 ` Felipe Balbi
2017-11-03 12:08 ` Greg Kroah-Hartman
2017-11-03 16:53 ` Johan Hovold
2017-11-04 10:40 ` Greg Kroah-Hartman
2017-11-05 12:53 ` Philippe Ombredanne
2017-11-05 13:51 ` Greg Kroah-Hartman
2017-11-05 15:39 ` Philippe Ombredanne
2017-11-06 8:17 ` Greg Kroah-Hartman
2017-11-09 9:51 ` Pavel Machek
2017-11-09 10:40 ` Greg Kroah-Hartman
2017-11-09 10:42 ` Pavel Machek
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=20171020184930.6b8815a5@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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).