From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spdx@vger.kernel.org
Subject: Re: [PATCH] export,module: add SPDX GPL-2.0 license identifier to headers with no license
Date: Thu, 14 Nov 2019 11:32:12 +0800 [thread overview]
Message-ID: <20191114033212.GA161229@kroah.com> (raw)
In-Reply-To: <CAK7LNAS3oYkaBTG+59prgu0Yqxn=2vi94mjHbKdx7TXBkPy5Xw@mail.gmail.com>
On Wed, Nov 13, 2019 at 08:46:11PM +0900, Masahiro Yamada wrote:
> On Fri, Oct 18, 2019 at 7:15 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Oct 18, 2019 at 01:50:53PM +0900, Masahiro Yamada wrote:
> > > Commit b24413180f56 ("License cleanup: add SPDX GPL-2.0 license
> > > identifier to files with no license") took care of a lot of files
> > > without any license information.
> > >
> > > These headers were not processed by the tool perhaps because they
> > > contain "GPL" in the code.
> > >
> > > I do not see any license boilerplate in them, so they fall back to
> > > GPL version 2 only, which is the project default.
> > >
> > > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >
> > Ah, nice catch!
> >
> > I'll queue this up to my spdx tree if no one objects.
> >
> > thanks,
> >
> > greg k-h
>
>
> No objection (comment) so far.
>
> I think it is OK to apply this.
Ok, will go do so, thanks.
greg k-h
prev parent reply other threads:[~2019-11-14 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 4:50 [PATCH] export,module: add SPDX GPL-2.0 license identifier to headers with no license Masahiro Yamada
2019-10-18 10:15 ` Greg Kroah-Hartman
2019-11-13 11:46 ` Masahiro Yamada
2019-11-14 3:32 ` Greg Kroah-Hartman [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=20191114033212.GA161229@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
/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.