From: hanyu001@208suo.com
To: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, liaochang1@huawei.com,
heiko.stuebner@vrull.eu, conor.dooley@microchip.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: kernel: remove space before ')'
Date: Mon, 17 Jul 2023 15:48:37 +0800 [thread overview]
Message-ID: <8ef63e3296f5628896f373d696a078f8@208suo.com> (raw)
In-Reply-To: <tencent_6B88A6697F6AB7CEBD04EEABA52ACDC66909@qq.com>
Fixes checkpatch errors:
riscv/kernel/probes:ERROR:space prohibited before that close parenthesis
')'
riscv/kernel/probes:ERROR:space prohibited before that close parenthesis
')'
riscv/kernel/probes:ERROR:space prohibited before that close parenthesis
')'
Signed-off-by: ztt <1549089851@qq.com>
---
arch/riscv/kernel/probes/simulate-insn.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/kernel/probes/simulate-insn.c
b/arch/riscv/kernel/probes/simulate-insn.c
index 7441ac8a6843..60792c79b42e 100644
--- a/arch/riscv/kernel/probes/simulate-insn.c
+++ b/arch/riscv/kernel/probes/simulate-insn.c
@@ -128,10 +128,10 @@ bool __kprobes simulate_auipc(u32 opcode, unsigned
long addr, struct pt_regs *re
(((opcode) >> 12) & 0x7)
#define branch_imm(opcode) \
- (((((opcode) >> 8) & 0xf ) << 1) | \
+ (((((opcode) >> 8) & 0xf) << 1) | \
((((opcode) >> 25) & 0x3f) << 5) | \
- ((((opcode) >> 7) & 0x1 ) << 11) | \
- ((((opcode) >> 31) & 0x1 ) << 12))
+ ((((opcode) >> 7) & 0x1) << 11) | \
+ ((((opcode) >> 31) & 0x1) << 12))
#define branch_offset(opcode) \
sign_extend32((branch_imm(opcode)), 12)
next parent reply other threads:[~2023-07-17 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_6B88A6697F6AB7CEBD04EEABA52ACDC66909@qq.com>
2023-07-17 7:48 ` hanyu001 [this message]
2023-07-17 8:03 ` 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=8ef63e3296f5628896f373d696a078f8@208suo.com \
--to=hanyu001@208suo.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=heiko.stuebner@vrull.eu \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®