From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Takashi Iwai <tiwai@suse.de>, Jiri Kosina <jikos@kernel.org>,
Ciaran Farrell <ciaran.farrell@suse.com>,
Christopher De Nicolo <cdenicolo@suse.com>,
Jeff Mahoney <jeffm@suse.com>, Vojtech Pavlik <vojtech@suse.cz>,
Mel Gorman <mgorman@suse.de>, Hannes Reinecke <hare@suse.de>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Russell King <rmk@armlinux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH 5/5] driver core: Remove redundant license text
Date: Thu, 9 Nov 2017 14:47:40 +0100 [thread overview]
Message-ID: <20171109134740.GD6545@kroah.com> (raw)
In-Reply-To: <20171108182630.GP22894@wotan.suse.de>
On Wed, Nov 08, 2017 at 07:26:30PM +0100, Luis R. Rodriguez wrote:
> On Tue, Nov 07, 2017 at 05:30:09PM +0100, Greg Kroah-Hartman wrote:
> > Now that the SPDX tag is in all driver core files, that identifies the
> > license in a specific and legally-defined manner.
>
> Takashi and Jiri mentioned that the effort to add SPDX tags to files which did
> not have licensing was discussed at the maintainers summit and it was agreed
> upon there that this made sense. That is wonderful.
>
> Naturally, even despite this, some still have their own questions about this
> work [0]. And some others seem to actually have pointed out that the work might
> have some technical issues [1] likely worth considering.
>
> [0] https://lkml.kernel.org/r/20171108151121.GC10374@infradead.org
> [1] https://lkml.kernel.org/r/20171108171938.7df66c65@alans-desktop
>
> > So the extra GPL text wording can be removed
>
> Highlight *removed*
>
> > as it is no longer needed at all.
>
> This secondary however was not.
Was not what? Discussed? Yes it was. I think the lwn.net article even
says so.
> But this begs the question that if there is still questions, issues pointed
> out, and request for a bit more open discussion about the *first* SPDX effort
> of adding a tag to files which have no license, if there was *any* due process
> for creating consensus for also going along with this *secondary* SPDX effort
> of license *simplification* by replacing old boiler plate license tags with an
> SPDX tag.
>
> At least internally within SUSE I can say so far that we are surprised by these
> patches and work. We did not know, and this is the first of communication of
> such effort.
>
> Don't get me wrong, these simplifications make perfect sense to me! But in
> dealing with licensing considerations before on Linux I've learned through
> feedback from you, Alan, and Ted and others to also be *extremely* careful and
> sensitive about licensing annotation matters, and this type of change seems to
> likely deserve a bit more community consensus than what this seems to be
> getting.
>
> Not even an RFC. So why rush this work in?
I don't post RFCs :)
As for "rush", not really, might as well do it sometime, so I've created
a bunch of patches and merged some of them. It's going to be a lot of
work, someone had to start it :)
Thomas is working on a document to describe this, hopefully it will be
done soon.
> > This is done on a quest to remove the 700+ different ways that files in
> > the kernel describe the GPL license text. And there's unneeded stuff
> > like the address (sometimes incorrect) for the FSF which is never
> > needed.
>
> Completely agreed, all this stuff is rather silly, however which tag is used,
> when, and how seems to have never been discussed and vetted anywhere to my
> knowledge.
"which" tag is just SPDX, that's easy. As for "when and how", I don't
understand the question.
> Below I leave two examples of the patch, but leave in place the diffstat.
I don't understand, do you object to the patches? Do you not think they
should be merged? If so, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-09 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:30 [PATCH 1/5] kobject: add SPDX identifiers to all kobject files Greg Kroah-Hartman
2017-11-07 16:30 ` [PATCH 2/5] kobject: Remove redundant license text Greg Kroah-Hartman
2017-11-07 16:30 ` [PATCH 3/5] driver core: add SPDX identifiers to all driver core files Greg Kroah-Hartman
2017-11-08 19:21 ` William Breathitt Gray
2017-11-07 16:30 ` [PATCH 4/5] drivers: core: arch_topology.c: move SPDX tag to top of the file Greg Kroah-Hartman
2017-11-07 16:30 ` [PATCH 5/5] driver core: Remove redundant license text Greg Kroah-Hartman
2017-11-08 18:26 ` Luis R. Rodriguez
2017-11-09 13:47 ` Greg Kroah-Hartman [this message]
2017-11-09 14:00 ` Christoph Hellwig
2017-11-09 16:44 ` Russell King
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=20171109134740.GD6545@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cdenicolo@suse.com \
--cc=ciaran.farrell@suse.com \
--cc=darrick.wong@oracle.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=jikos@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@suse.de \
--cc=pombredanne@nexb.com \
--cc=rmk@armlinux.org.uk \
--cc=tiwai@suse.de \
--cc=tytso@mit.edu \
--cc=vojtech@suse.cz \
/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).