From: kernel test robot <lkp@intel.com>
To: Guo Ren <guoren@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Björn Töpel" <bjorn@rivosinc.com>
Subject: [linux-next:master 5598/8375] arch/riscv/include/asm/syscall.h:87 syscall_handler() warn: inconsistent indenting
Date: Sun, 2 Apr 2023 10:11:17 +0800 [thread overview]
Message-ID: <202304021048.J6a5T08T-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4b0f4525dc4fe8af17b3daefe585f0c2eb0fe0a5
commit: f0bddf50586da81360627a772be0e355b62f071e [5598/8375] riscv: entry: Convert to generic entry
config: riscv-randconfig-m031-20230402 (https://download.01.org/0day-ci/archive/20230402/202304021048.J6a5T08T-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304021048.J6a5T08T-lkp@intel.com/
smatch warnings:
arch/riscv/include/asm/syscall.h:87 syscall_handler() warn: inconsistent indenting
vim +87 arch/riscv/include/asm/syscall.h
76
77 typedef long (*syscall_t)(ulong, ulong, ulong, ulong, ulong, ulong, ulong);
78 static inline void syscall_handler(struct pt_regs *regs, ulong syscall)
79 {
80 syscall_t fn;
81
82 #ifdef CONFIG_COMPAT
83 if ((regs->status & SR_UXL) == SR_UXL_32)
84 fn = compat_sys_call_table[syscall];
85 else
86 #endif
> 87 fn = sys_call_table[syscall];
88
89 regs->a0 = fn(regs->orig_a0, regs->a1, regs->a2,
90 regs->a3, regs->a4, regs->a5, regs->a6);
91 }
92
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-02 2:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202304021048.J6a5T08T-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn@rivosinc.com \
--cc=guoren@linux.alibaba.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.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