From: Thomas Gleixner <tglx@linutronix.de>
To: Nishad Kamdar <nishadkamdar@gmail.com>
Cc: "Greentime Hu" <green.hu@gmail.com>,
"Vincent Chen" <deanbo422@gmail.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"Will Deacon" <will.deacon@arm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Nick Piggin" <npiggin@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Joe Perches" <joe@perches.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 2/5] nds32: Use the correct style for SPDX License Identifier
Date: Tue, 16 Apr 2019 20:35:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904162034260.1780@nanos.tec.linutronix.de> (raw)
In-Reply-To: <f6a7c31f4e8b743a2877875ac3fc49ecb8b9eb0c.1555427419.git.nishadkamdar@gmail.com>
On Tue, 16 Apr 2019, Nishad Kamdar wrote:
> This patch corrects the SPDX License Identifier style
> in the nds32 Hardware Architecture related files.
>
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
Actually instead of doing that we should fix the documentation. The
requirement came from older binutils because they barfed on // style
comments in ASM files. That's history as we upped the minimal binutil
requirement.
Thanks,
tglx
next prev parent reply other threads:[~2019-04-16 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1555427418.git.nishadkamdar@gmail.com>
2019-04-16 15:24 ` Nishad Kamdar
2019-04-16 18:35 ` Thomas Gleixner [this message]
2019-04-29 14:20 ` Nishad Kamdar
2019-04-23 17:14 ` Souptick Joarder
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=alpine.DEB.2.21.1904162034260.1780@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishadkamdar@gmail.com \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=will.deacon@arm.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