From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: freescale: Update to use SPDX identifiers
Date: Tue, 19 Jun 2018 11:09:33 +0800 [thread overview]
Message-ID: <20180619030931.GD16091@dragon> (raw)
In-Reply-To: <1528828122-9276-1-git-send-email-leoyang.li@nxp.com>
On Tue, Jun 12, 2018 at 01:28:42PM -0500, Li Yang wrote:
> Replace license text with corresponding SPDX identifiers and update the
> format of existing SPDX identifiers to follow the new guideline
> Documentation/process/license-rules.rst.
>
> Note that some of the files mentioned X11 license previously but the
> license text actually matches MIT license.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2018-06-19 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 18:28 [PATCH] arm64: dts: freescale: Update to use SPDX identifiers Li Yang
2018-06-12 18:32 ` Fabio Estevam
2018-06-12 18:50 ` Li Yang
2018-06-19 3:09 ` Shawn Guo [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=20180619030931.GD16091@dragon \
--to=shawnguo@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox