From: Nishad Kamdar <nishadkamdar@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Joe Perches <joe@perches.com>, Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARCH: Use the correct style for SPDX License Identifier
Date: Mon, 8 Apr 2019 19:00:18 +0530 [thread overview]
Message-ID: <20190408133016.GA2662@nishad> (raw)
In-Reply-To: <20190331010549.GA17669@bogus>
On Sun, Mar 31, 2019 at 01:41:26AM -0500, Rob Herring wrote:
> On Sat, Mar 23, 2019 at 06:58:14PM +0530, Nishad Kamdar wrote:
> > This patch corrects the SPDX License Identifier style
> > in the Hardware Architecture subsystem.
> >
> > Changes made by using a script provided by Joe Perches here:
> > https://lkml.org/lkml/2019/2/7/46
> > and making some manual changes.
> >
> > Suggested-by: Joe Perches <joe@perches.com>
> > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > ---
> > arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 2 +-
> > arch/arm64/include/asm/pointer_auth.h | 2 +-
> > arch/arm64/include/asm/sdei.h | 2 +-
> > arch/arm64/include/asm/vmap_stack.h | 2 +-
> > arch/nds32/include/asm/assembler.h | 2 +-
>
> No reason to put all arches in one patch. Please split by arch for
> maintainers to take.
>
> Rob
>
Ok, I'll do that.
Thanks for the review.
Thanks and regards,
Nishad
prev parent reply other threads:[~2019-04-08 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 13:28 [PATCH] ARCH: Use the correct style for SPDX License Identifier Nishad Kamdar
2019-03-23 20:59 ` Uwe Kleine-König
2019-03-30 22:04 ` Nishad Kamdar
2019-03-31 6:41 ` Rob Herring
2019-04-08 13:30 ` Nishad Kamdar [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=20190408133016.GA2662@nishad \
--to=nishadkamdar@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).