From: kernel test robot <lkp@intel.com>
To: Will Deacon <will@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [arm-perf:overflow-stack 10/13] arch/arm64/include/asm/sdei.h:49:15: error: expected identifier or '('
Date: Fri, 31 Jul 2026 02:15:51 +0800 [thread overview]
Message-ID: <202607310259.hYhBng05-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git overflow-stack
head: 7c0748c59a858f301fc801a9818ea1c11ff88ff0
commit: d017f75e2f157a38b824c8f4253f07fac65622eb [10/13] arm64: entry: Point SP_EL0 at the overflow stack
config: arm64-randconfig-002-20260730 (https://download.01.org/0day-ci/archive/20260731/202607310259.hYhBng05-lkp@intel.com/config)
compiler: clang version 21.1.8 (https://github.com/llvm/llvm-project 2078da43e25a4623cab2d0d60decddf709aaea28)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260731/202607310259.hYhBng05-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607310259.hYhBng05-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/arm64/kernel/smp.c:52:
In file included from arch/arm64/include/asm/stacktrace.h:16:
>> arch/arm64/include/asm/sdei.h:49:15: error: expected identifier or '('
49 | unsigned long sdei_arch_get_entry_point(int conduit);
| ^
include/linux/arm_sdei.h:16:45: note: expanded from macro 'sdei_arch_get_entry_point'
16 | #define sdei_arch_get_entry_point(conduit) (0)
| ^
In file included from arch/arm64/kernel/smp.c:52:
In file included from arch/arm64/include/asm/stacktrace.h:16:
>> arch/arm64/include/asm/sdei.h:49:15: error: expected ')'
include/linux/arm_sdei.h:16:45: note: expanded from macro 'sdei_arch_get_entry_point'
16 | #define sdei_arch_get_entry_point(conduit) (0)
| ^
arch/arm64/include/asm/sdei.h:49:15: note: to match this '('
include/linux/arm_sdei.h:16:44: note: expanded from macro 'sdei_arch_get_entry_point'
16 | #define sdei_arch_get_entry_point(conduit) (0)
| ^
In file included from arch/arm64/kernel/smp.c:52:
In file included from arch/arm64/include/asm/stacktrace.h:16:
arch/arm64/include/asm/sdei.h:50:9: warning: 'sdei_arch_get_entry_point' macro redefined [-Wmacro-redefined]
50 | #define sdei_arch_get_entry_point(x) sdei_arch_get_entry_point(x)
| ^
include/linux/arm_sdei.h:16:9: note: previous definition is here
16 | #define sdei_arch_get_entry_point(conduit) (0)
| ^
1 warning and 2 errors generated.
vim +49 arch/arm64/include/asm/sdei.h
5cd474e57368f0 D Scott Phillips 2023-06-26 37
f5df26961853d6 James Morse 2018-01-08 38 /*
f5df26961853d6 James Morse 2018-01-08 39 * The above entry point does the minimum to call C code. This function does
f5df26961853d6 James Morse 2018-01-08 40 * anything else, before calling the driver.
f5df26961853d6 James Morse 2018-01-08 41 */
f5df26961853d6 James Morse 2018-01-08 42 struct sdei_registered_event;
f5df26961853d6 James Morse 2018-01-08 43 asmlinkage unsigned long __sdei_handler(struct pt_regs *regs,
f5df26961853d6 James Morse 2018-01-08 44 struct sdei_registered_event *arg);
f5df26961853d6 James Morse 2018-01-08 45
d60b228fd19985 Mark Rutland 2021-06-07 46 unsigned long do_sdei_event(struct pt_regs *regs,
d60b228fd19985 Mark Rutland 2021-06-07 47 struct sdei_registered_event *arg);
d60b228fd19985 Mark Rutland 2021-06-07 48
f5df26961853d6 James Morse 2018-01-08 @49 unsigned long sdei_arch_get_entry_point(int conduit);
f5df26961853d6 James Morse 2018-01-08 50 #define sdei_arch_get_entry_point(x) sdei_arch_get_entry_point(x)
f5df26961853d6 James Morse 2018-01-08 51
:::::: The code at line 49 was first introduced by commit
:::::: f5df26961853d6809d704cedcaf082c57f635a64 arm64: kernel: Add arch-specific SDEI entry code and CPU masking
:::::: TO: James Morse <james.morse@arm.com>
:::::: CC: Catalin Marinas <catalin.marinas@arm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-30 18:16 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=202607310259.hYhBng05-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=will@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