2020-12-22 08:40:44

by Yanteng Si

[permalink] [raw]
Subject: [PATCH] MIPS: loongson64: smp.c: Fix block comment coding style

From: siyanteng <[email protected]>

This patch fixes:
"WARNING: Block comments use a trailing */ on a separate line"
by checkpatch.pl

Signed-off-by: siyanteng <[email protected]>
---
arch/mips/loongson64/smp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/arch/mips/loongson64/smp.c b/arch/mips/loongson64/smp.c
index b8c1fc3158fd..459ea5b7a1b0 100644
--- a/arch/mips/loongson64/smp.c
+++ b/arch/mips/loongson64/smp.c
@@ -483,7 +483,8 @@ static void __init loongson3_smp_setup(void)
init_cpu_possible(cpu_none_mask);

/* For unified kernel, NR_CPUS is the maximum possible value,
- * loongson_sysconf.nr_cpus is the really present value */
+ * loongson_sysconf.nr_cpus is the really present value
+ */
while (i < loongson_sysconf.nr_cpus) {
if (loongson_sysconf.reserved_cpus_mask & (1<<i)) {
/* Reserved physical CPU cores */
@@ -567,7 +568,8 @@ static void loongson3_cpu_die(unsigned int cpu)
/* To shutdown a core in Loongson 3, the target core should go to CKSEG1 and
* flush all L1 entries at first. Then, another core (usually Core 0) can
* safely disable the clock of the target core. loongson3_play_dead() is
- * called via CKSEG1 (uncached and unmmaped) */
+ * called via CKSEG1 (uncached and unmmaped)
+ */
static void loongson3_type1_play_dead(int *state_addr)
{
register int val;
--
2.27.0


2021-01-04 10:51:25

by Thomas Bogendoerfer

[permalink] [raw]
Subject: Re: [PATCH] MIPS: loongson64: smp.c: Fix block comment coding style

On Tue, Dec 22, 2020 at 04:37:00PM +0800, [email protected] wrote:
> From: siyanteng <[email protected]>
>
> This patch fixes:
> "WARNING: Block comments use a trailing */ on a separate line"
> by checkpatch.pl
>
> Signed-off-by: siyanteng <[email protected]>
> ---
> 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 ]