From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spdx@vger.kernel.org
Subject: Re: [GIT PULL] SPDX update for 5.2-rc3 - round 1
Date: Fri, 31 May 2019 06:24:00 -0700 [thread overview]
Message-ID: <20190531132400.GA5518@kroah.com> (raw)
In-Reply-To: <CAMuHMdV=95sKB+h_pf45DiYeiJzrk1L=014Tj8Y04_hPyRMBNQ@mail.gmail.com>
On Fri, May 31, 2019 at 09:17:06AM +0200, Geert Uytterhoeven wrote:
> Hi Greg, Thomas,
>
> On Fri, May 31, 2019 at 3:49 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:
> >
> > Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/spdx-5.2-rc3-1
> >
> > for you to fetch changes up to 96ac6d435100450f0565708d9b885ea2a7400e0a:
> >
> > treewide: Add SPDX license identifier - Kbuild (2019-05-30 11:32:33 -0700)
> >
> > ----------------------------------------------------------------
> > SPDX update for 5.2-rc3, round 1
> >
> > Here is another set of reviewed patches that adds SPDX tags to different
> > kernel files, based on a set of rules that are being used to parse the
> > comments to try to determine that the license of the file is
> > "GPL-2.0-or-later" or "GPL-2.0-only". Only the "obvious" versions of
> > these matches are included here, a number of "non-obvious" variants of
> > text have been found but those have been postponed for later review and
> > analysis.
> >
> > There is also a patch in here to add the proper SPDX header to a bunch
> > of Kbuild files that we have missed in the past due to new files being
> > added and forgetting that Kbuild uses two different file names for
> > Makefiles. This issue was reported by the Kbuild maintainer.
> >
> > These patches have been out for review on the linux-spdx@vger mailing
> > list, and while they were created by automatic tools, they were
> > hand-verified by a bunch of different people, all whom names are on the
> > patches are reviewers.
> >
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> I'm sorry, but as long[*] as this does not conform to
> Documentation/process/license-rules.rst, I have to provide my:
> NAked-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> [*] The obvious solution is to update Documentation/process/license-rules.rst,
> as people have asked before.
I don't understand, what does not conform? We are trying _to_ conform
to that file, what did we do wrong?
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-31 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190531014808.GA30932@kroah.com>
2019-05-31 7:17 ` [GIT PULL] SPDX update for 5.2-rc3 - round 1 Geert Uytterhoeven
2019-05-31 13:24 ` Greg KH [this message]
2019-05-31 13:51 ` Geert Uytterhoeven
2019-05-31 14:02 ` Greg KH
2019-05-31 14:58 ` Geert Uytterhoeven
2019-05-31 15:05 ` Greg KH
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=20190531132400.GA5518@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--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 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.