From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: siyanteng@loongson.cn
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhuacai@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: loongson64: smp.c: Fix block comment coding style
Date: Mon, 4 Jan 2021 11:43:57 +0100 [thread overview]
Message-ID: <20210104104357.GE4765@alpha.franken.de> (raw)
In-Reply-To: <20201222083700.3651527-1-siyanteng@loongson.cn>
On Tue, Dec 22, 2020 at 04:37:00PM +0800, siyanteng@loongson.cn wrote:
> From: siyanteng <siyanteng@loongson.cn>
>
> This patch fixes:
> "WARNING: Block comments use a trailing */ on a separate line"
> by checkpatch.pl
>
> Signed-off-by: siyanteng <siyanteng@loongson.cn>
> ---
> arch/mips/loongson64/smp.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-01-04 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 8:37 siyanteng
2021-01-04 10:43 ` Thomas Bogendoerfer [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=20210104104357.GE4765@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=siyanteng@loongson.cn \
/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
all inboxes | Powered by JetHome®