From: kernel test robot <lkp@intel.com>
To: Anup Patel <anup.patel@wdc.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [PATCH] RISC-V: fix semicolon.cocci warnings
Date: Fri, 31 Dec 2021 20:12:06 +0800 [thread overview]
Message-ID: <20211231121206.GA2749@e375fe33811b> (raw)
From: kernel test robot <lkp@intel.com>
arch/riscv/kernel/smp.c:130:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Anup Patel <anup.patel@wdc.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tree: https://github.com/avpatel/linux.git riscv_kvm_aia_v1
head: 6fa93cde61f5f84422bd3f97b9db6e2406a344dd
commit: dea7752f30104c9bb3c2c67ce2c56e5a5eb3c290 [17/42] RISC-V: Treat IPIs as normal Linux IRQs
:::::: branch date: 6 hours ago
:::::: commit date: 3 days ago
smp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/riscv/kernel/smp.c
+++ b/arch/riscv/kernel/smp.c
@@ -127,7 +127,7 @@ static irqreturn_t handle_IPI(int irq, v
default:
pr_warn("CPU%d: unhandled IPI%d\n", smp_processor_id(), ipi);
break;
- };
+ }
return IRQ_HANDLED;
}
next reply other threads:[~2021-12-31 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 12:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-29 21:57 [avpatel:riscv_aia_v1 3/21] arch/riscv/kernel/smp.c:120:2-3: Unneeded semicolon kernel test robot
2022-01-29 21:03 ` [PATCH] RISC-V: fix semicolon.cocci warnings kernel test robot
2022-04-05 10:35 [avpatel:riscv_kvm_aia_v1 9/29] arch/riscv/kernel/smp.c:120:2-3: Unneeded semicolon kernel test robot
2022-04-05 10:33 ` [PATCH] RISC-V: fix semicolon.cocci warnings kernel test robot
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=20211231121206.GA2749@e375fe33811b \
--to=lkp@intel.com \
--cc=anup.patel@wdc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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