public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Frank Rowand <frowand.list@gmail.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] scripts/dtc: Update to upstream version v1.5.0-30-g702c1b6c0e73
Date: Fri, 21 Jun 2019 16:54:44 +0200	[thread overview]
Message-ID: <20190621145444.GB6313@kroah.com> (raw)
In-Reply-To: <20190621142900.31988-1-robh@kernel.org>

On Fri, Jun 21, 2019 at 08:29:00AM -0600, Rob Herring wrote:
> Pull in SPDX tag conversion from upstream dtc. This will replace the
> conversion done in the kernel tree copy in v5.2-rc2.
> 
> This adds the following commits from upstream:
> 
> 702c1b6c0e73 README.license: Update to reflect SPDX tag usage
> 4097bbffcf1d dtc: Add GPLv2 SPDX tags to files missing license text
> 94f87cd5b7c5 libfdt: Add dual GPL/BSD SPDX tags to files missing license text
> c4ffc05574b1 tests: Replace license boilerplate with SPDX tags
> a5ac29baacd2 pylibfdt: Replace dual GPLv2/BSD license boilerplate with SPDX tags
> 7fb0f4db2eb7 libfdt: Replace GPL/BSD boilerplate/reference with SPDX tags
> acfe84f2c47e dtc: Replace GPLv2 boilerplate/reference with SPDX tags
> 
> Signed-off-by: Rob Herring <robh@kernel.org>

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

      reply	other threads:[~2019-06-21 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 14:29 [PATCH] scripts/dtc: Update to upstream version v1.5.0-30-g702c1b6c0e73 Rob Herring
2019-06-21 14:54 ` 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=20190621145444.GB6313@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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