Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [bvanassche:thread-safety 416/438] arch/arm/mach-mvebu/cpu-reset.c:101:1: error: expected ';' after top level declarator
Date: Sat, 14 Nov 2026 07:03:16 +0800	[thread overview]
Message-ID: <202611140612.OYIpyuMW-lkp@intel.com> (raw)

tree:   https://github.com/bvanassche/linux thread-safety
head:   8ea0e62cf4d68a895e3152c92a5f6ead6d5c9554
commit: 0efee98d1b3338e5fb967e0805d802cdb7953d42 [416/438] fs: Annotate kill_sb() callbacks with __releases(&sb->s_umount)
config: arm-defconfig (https://download.01.org/0day-ci/archive/20261114/202611140612.OYIpyuMW-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 1b1fed44d3dcca649a9877915d57c3357a98124e)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261114/202611140612.OYIpyuMW-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/202611140612.OYIpyuMW-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/arm/mach-mvebu/cpu-reset.c:101:1: error: expected ';' after top level declarator
     101 | early_initcall(mvebu_cpu_reset_init);
         | ^
   include/linux/init.h:284:29: note: expanded from macro 'early_initcall'
     284 | #define early_initcall(fn)              __define_initcall(fn, early)
         |                                         ^
   include/linux/init.h:277:35: note: expanded from macro '__define_initcall'
     277 | #define __define_initcall(fn, id) ___define_initcall(fn, id, .initcall##id)
         |                                   ^
   include/linux/init.h:275:35: note: expanded from macro '___define_initcall'
     275 |         __unique_initcall(fn, id, __sec, __initcall_id(fn))
         |                                          ^
   note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
   <command line>:8:26: note: expanded from macro '__KBUILD_MODNAME'
       8 | #define __KBUILD_MODNAME cpu_reset
         |                          ^
   arch/arm/include/asm/proc-fns.h:137:21: note: expanded from macro 'cpu_reset'
     137 | #define cpu_reset                       PROC_VTABLE(reset)
         |                                         ^
   arch/arm/include/asm/proc-fns.h:126:35: note: expanded from macro 'PROC_VTABLE'
     126 | #define PROC_VTABLE(f)                  processor.f
         |                                                  ^
   1 error generated.


vim +101 arch/arm/mach-mvebu/cpu-reset.c

3f20fb1153b374 Thomas Petazzoni 2014-04-14  100  
3f20fb1153b374 Thomas Petazzoni 2014-04-14 @101  early_initcall(mvebu_cpu_reset_init);

:::::: The code at line 101 was first introduced by commit
:::::: 3f20fb1153b374737acd40d42cb3cab2ae5dae35 ARM: mvebu: introduce CPU reset code

:::::: TO: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
:::::: CC: Jason Cooper <jason@lakedaemon.net>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-11-13 23:03 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=202611140612.OYIpyuMW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bvanassche@acm.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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