linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hanyu001@208suo.com
To: paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, atishp@rivosinc.com, maz@kernel.org,
	apatel@ventanamicro.com, guoren@kernel.org,
	sunilvl@ventanamicro.com, ben-linux@fluff.org,
	vschneid@redhat.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: kernel: insert space before the open parenthesis '('
Date: Mon, 17 Jul 2023 16:06:11 +0800	[thread overview]
Message-ID: <b90d162c4fb8062355634fb53b05173d@208suo.com> (raw)
In-Reply-To: <tencent_7D5EADDF79970079F568A5C4F801910DED06@qq.com>

Fix below checkpatch error:

/riscv/kernel/smp.c:93:ERROR: space required before the open parenthesis 
'('

Signed-off-by: ztt <1549089851@qq.com>
---
  arch/riscv/kernel/smp.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/riscv/kernel/smp.c b/arch/riscv/kernel/smp.c
index 23e533766a49..1454f2415b7f 100644
--- a/arch/riscv/kernel/smp.c
+++ b/arch/riscv/kernel/smp.c
@@ -90,7 +90,7 @@ static inline void ipi_cpu_crash_stop(unsigned int 
cpu, struct pt_regs *regs)
          cpu_ops[cpu]->cpu_stop();
  #endif

-    for(;;)
+    for (;;)
          wait_for_interrupt();
  }
  #else

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

       reply	other threads:[~2023-07-17  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_7D5EADDF79970079F568A5C4F801910DED06@qq.com>
2023-07-17  8:06 ` hanyu001 [this message]
2023-07-17  8:14   ` [PATCH] riscv: kernel: insert space before the open parenthesis '(' Conor Dooley

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=b90d162c4fb8062355634fb53b05173d@208suo.com \
    --to=hanyu001@208suo.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@rivosinc.com \
    --cc=ben-linux@fluff.org \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=vschneid@redhat.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;
as well as URLs for NNTP newsgroup(s).