All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: [GIT PULL] SPDX update for 5.2-rc3 - round 2
Date: Sun, 2 Jun 2019 08:39:05 +0200	[thread overview]
Message-ID: <20190602063905.GA14513@kroah.com> (raw)

The following changes since commit 2f4c53349961c8ca480193e47da4d44fdb8335a8:

  Merge tag 'spdx-5.2-rc3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core (2019-05-31 08:34:32 -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-2

for you to fetch changes up to 8e82fe2ab65a80b1526b285c661ab88cc5891e3a:

  treewide: fix typos of SPDX-License-Identifier (2019-06-01 18:29:58 +0200)

----------------------------------------------------------------
SPDX fixes for 5.2-rc3, round 2

Here are just two small patches, that fix up some found SPDX identifier
issues.

The first patch fixes an error in a previous SPDX fixup patch, that
causes build errors when doing 'make clean' on the tree (the fact that
almost no one noticed it reflects the fact that kernel developers don't
like doing that option very often...)

The second patch fixes up a number of places in the tree where people
mistyped the string "SPDX-License-Identifier".  Given that people can
not even type their own name all the time without mistakes, this was
bound to happen, and odds are, we will have to add some type of check
for this to checkpatch.pl to catch this happening in the future.

Both of these have passed testing by 0-day.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Alex Xu (Hello71) (1):
      crypto: ux500 - fix license comment syntax error

Masahiro Yamada (1):
      treewide: fix typos of SPDX-License-Identifier

 arch/arm/kernel/bugs.c                | 2 +-
 drivers/crypto/ux500/cryp/Makefile    | 2 +-
 drivers/phy/st/phy-stm32-usbphyc.c    | 2 +-
 drivers/pinctrl/sh-pfc/pfc-r8a77980.c | 2 +-
 lib/test_stackinit.c                  | 2 +-
 sound/soc/codecs/max9759.c            | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

             reply	other threads:[~2019-06-02  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02  6:39 Greg KH [this message]
2019-06-02 12:03 ` [GIT PULL] SPDX update for 5.2-rc3 - round 2 Masahiro Yamada
2019-06-02 17:15   ` Greg KH
2019-06-03  0:15     ` Masahiro Yamada
2019-06-03  7:38       ` Greg KH
2019-06-02 15:04 ` Joe Perches
2019-06-02 17:25 ` pr-tracker-bot

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=20190602063905.GA14513@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.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.