From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Kate Stewart <kate@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Rob Herring <rob.herring@linaro.org>,
Jonas Oberg <jonas@fsfe.org>, Joe Perches <joe@perches.com>,
linux-xfs@vger.kernel.org
Subject: Re: [patch 0/7] LICENSES: Add documentation and initial License files
Date: Tue, 14 Nov 2017 10:15:16 +0000 [thread overview]
Message-ID: <20171114101516.GN12318@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20171112191821.240484206@linutronix.de>
On Sun, Nov 12, 2017 at 08:18:21PM +0100, Thomas Gleixner wrote:
> Folks!
>
> First of all I want to apologize for the suboptimal process which brought
> this initial SPDX annotation into the kernel. We surely should have posted
> exactly this patch series first, but we were too focused on the actual
> annotation and analysis work, which took place in the last 10 months. As is
> happens often with work which occupies one on the 'technical' level
> completely, documentation is the last thing to think of.
Hi Thomas,
Thank you for doing this, this addresses many of my concerns with the
SPDX license tagging. For the series:
Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
As for the comment style, I'm sure that we'll eventually learn to use
the appropriate style for the file type, but I suspect it won't be
easy as it's not intuitive.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
prev parent reply other threads:[~2017-11-14 10:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 19:18 [patch 0/7] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-11-12 19:18 ` [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-11-12 19:54 ` Joe Perches
2017-11-12 19:57 ` Thomas Gleixner
2017-11-12 20:07 ` Jonathan Corbet
2017-11-12 20:19 ` Thomas Gleixner
2017-11-13 10:04 ` [1/7] " Charlemagne Lasse
2017-11-13 12:26 ` Thomas Gleixner
2017-11-13 12:40 ` Charlemagne Lasse
2017-11-13 13:26 ` Thomas Gleixner
2017-11-16 15:07 ` [patch 1/7] " Jonathan Corbet
2017-11-16 15:15 ` Jonas Oberg
2017-11-16 18:03 ` Thomas Gleixner
2017-11-17 7:37 ` Philippe Ombredanne
2017-11-17 8:57 ` Greg Kroah-Hartman
2017-11-17 10:53 ` Philippe Ombredanne
2017-11-17 12:29 ` Greg Kroah-Hartman
2017-11-12 19:18 ` [patch 2/7] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-11-14 18:02 ` Rob Herring
2017-11-14 19:05 ` Greg Kroah-Hartman
2017-11-16 11:46 ` Jonas Oberg
2017-11-16 13:12 ` Thomas Gleixner
2017-11-12 19:18 ` [patch 3/7] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-11-12 19:18 ` [patch 4/7] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-11-12 19:18 ` [patch 5/7] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-11-12 19:18 ` [patch 6/7] LICENSES: Add the MIT license Thomas Gleixner
2017-11-12 19:18 ` [patch 7/7] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-11-12 20:02 ` [patch 0/7] LICENSES: Add documentation and initial License files Joe Perches
2017-11-12 20:55 ` Thomas Gleixner
2017-11-13 13:54 ` Philippe Ombredanne
2017-11-14 10:15 ` Russell King - ARM Linux [this message]
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=20171114101516.GN12318@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=akpm@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=jonas@fsfe.org \
--cc=kate@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=rob.herring@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.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).