All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
	"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: [jimc:scratchpad-v10 13/24] kernel/locking/lockdep.c:71:33: error: too many arguments provided to function-like macro invocation
Date: Sun, 23 Aug 2026 20:26:25 +0800	[thread overview]
Message-ID: <202608230104.rEFLxzxH-lkp@intel.com> (raw)

tree:   https://github.com/jimc/linux.git scratchpad-v10
head:   a23fc077806416450fbeb0a5a534fd995e465430
commit: c64a3f08a0141ea44aaf52cb647a97400c5e1dd0 [13/24] locking/lockdep: Allocate list_entries from static bootstrap scratchrec pool
config: x86_64-randconfig-001-20260822 (https://download.01.org/0day-ci/archive/20260823/202608230104.rEFLxzxH-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260823/202608230104.rEFLxzxH-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/202608230104.rEFLxzxH-lkp@intel.com/

Note: the jimc/scratchpad-v10 HEAD a23fc077806416450fbeb0a5a534fd995e465430 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

>> kernel/locking/lockdep.c:71:33: error: too many arguments provided to function-like macro invocation
      71 |                                SCRATCH_64K_ORDER, 0, &lockdep_pool_key);
         |                                                      ^
   include/linux/scratchpad.h:360:9: note: macro 'SCRATCHREC_INIT_STATIC' defined here
     360 | #define SCRATCHREC_INIT_STATIC(name, _elem_size, _static_buf, _size_bytes, _min_order, _key) \
         |         ^
>> kernel/locking/lockdep.c:69:2: error: use of undeclared identifier 'SCRATCHREC_INIT_STATIC'
      69 |         SCRATCHREC_INIT_STATIC(lockdep_pool, sizeof(struct lock_list),
         |         ^~~~~~~~~~~~~~~~~~~~~~
   2 errors generated.


vim +71 kernel/locking/lockdep.c

    66	
    67	DEFINE_STATIC_KEY_TRUE(lockdep_pool_key);
    68	static struct scratchrec lockdep_pool =
  > 69		SCRATCHREC_INIT_STATIC(lockdep_pool, sizeof(struct lock_list),
    70				       list_entries, sizeof(list_entries),
  > 71				       SCRATCH_64K_ORDER, 0, &lockdep_pool_key);
    72	

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

                 reply	other threads:[~2026-08-23 12:26 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=202608230104.rEFLxzxH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jim.cromie@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ukaszb@chromium.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.