linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kate Stewart <kstewart@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-spdx@vger.kernel.org
Subject: Re: Missing SPDX tags for Kbuild files
Date: Thu, 30 May 2019 07:01:01 -0500	[thread overview]
Message-ID: <CAG_66ZS=uP1g1Qjm6juDDaA1SOeE6hC0yfBAqSPbi6Vhvg045A@mail.gmail.com> (raw)
In-Reply-To: <20190530115256.GA30967@kroah.com>

On Thu, May 30, 2019 at 6:53 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, May 30, 2019 at 05:58:05PM +0900, Masahiro Yamada wrote:
> > Hi.
> >
> >
> > Recently, "Makefiles",  "Kconfig" files were given with SPDX License tags.
> >
> > Author: Thomas Gleixner <tglx@linutronix.de>
> > Date:   Sun May 19 13:07:45 2019 +0100
> >
> >     treewide: Add SPDX license identifier - Makefile/Kconfig
> >
> >
> >
> >
> > But, the file name "Kbuild" is also a Makefile.
> >
> > Conventionally, Linux build system uses both "Kbuild" and "Makefile".
> >
> >
> > For example, SPDX tag is missing in
> >
> > arch/x86/Kbuild
> > arch/x86/include/uapi/asm/Kbuild
> > arch/x86/include/asm/Kbuild
> >
> >
> > Will somebody work on "Kbuild" files please ?
>
> Sure, how about the attached patch, any objection to me queueing it up?

Thanks Greg.

Thomas' initial patch fixed a bunch of these in the initial cleanup,
but I guess
more were added (and overlooked since then).

Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>

  reply	other threads:[~2019-05-30 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  8:58 Missing SPDX tags for Kbuild files Masahiro Yamada
2019-05-30 11:52 ` Greg KH
2019-05-30 12:01   ` Kate Stewart [this message]
2019-05-30 18:31     ` Greg KH
2019-05-31  0:40       ` Masahiro Yamada
2019-05-31  1:17         ` Greg KH
2019-05-30 12:01   ` Greg KH
2019-05-30 12:03   ` [PATCH v2] treewide: Add SPDX license identifier - Kbuild Greg Kroah-Hartman

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='CAG_66ZS=uP1g1Qjm6juDDaA1SOeE6hC0yfBAqSPbi6Vhvg045A@mail.gmail.com' \
    --to=kstewart@linuxfoundation.org \
    --cc=gregkh@linuxfoundation.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 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).