From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [PATCH] RISC-V: fix semicolon.cocci warnings
Date: Fri, 19 Mar 2021 13:52:31 +0800 [thread overview]
Message-ID: <20210319055231.GA1034@67f04c9205e7> (raw)
In-Reply-To: <202103191321.bagpcyFZ-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
From: kernel test robot <lkp@intel.com>
drivers/perf/riscv_pmu.c:65:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: 5009c84a60b9 ("RISC-V: Add a perf platform driver")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tree: https://github.com/atishp04/linux sbi_pmu_v1
head: d82bc37d5a962b33af712da468a82d2ced9eb194
commit: 5009c84a60b998b44c7c8481984b5553bfc0986c [11/14] RISC-V: Add a perf platform driver
riscv_pmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/perf/riscv_pmu.c
+++ b/drivers/perf/riscv_pmu.c
@@ -62,7 +62,7 @@ unsigned long csr_read_num(int csr_num)
switchcase_csr_read_32(CSR_CYCLEH, ret)
default :
break;
- };
+ }
return ret;
next prev parent reply other threads:[~2021-03-19 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 5:52 [atishp04:sbi_pmu_v1 11/14] drivers/perf/riscv_pmu.c:65:2-3: Unneeded semicolon kernel test robot
2021-03-19 5:52 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-31 12:12 [PATCH] RISC-V: fix semicolon.cocci warnings kernel test robot
2021-12-31 12:12 ` kernel test robot
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-01-29 21:03 ` 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=20210319055231.GA1034@67f04c9205e7 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.