The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nam Cao <namcao@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [tip:timers/cleanups 5/10] kernel/time/timer_list.c:49:77: error: too few arguments provided to function-like macro invocation
Date: Sat, 5 Apr 2025 01:04:04 +0800	[thread overview]
Message-ID: <202504050045.fyyfMGEQ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/cleanups
head:   5c4da3a96bf484f965057c281f1ef48ac46987bc
commit: 9453228aa82f20c07670d22c3d54f1be6c4244b4 [5/10] hrtimers: Make callback function pointer private
config: hexagon-randconfig-002-20250404 (https://download.01.org/0day-ci/archive/20250405/202504050045.fyyfMGEQ-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 92c93f5286b9ff33f27ff694d2dc33da1c07afdd)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250405/202504050045.fyyfMGEQ-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/202504050045.fyyfMGEQ-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/time/timer_list.c:49:77: error: too few arguments provided to function-like macro invocation
      49 |         SEQ_printf(m, " #%d: <%p>, %ps", idx, taddr, ACCESS_PRIVATE(timer->function));
         |                                                                                    ^
   include/linux/compiler_types.h:78:10: note: macro 'ACCESS_PRIVATE' defined here
      78 | # define ACCESS_PRIVATE(p, member) ((p)->member)
         |          ^
>> kernel/time/timer_list.c:49:47: error: use of undeclared identifier 'ACCESS_PRIVATE'
      49 |         SEQ_printf(m, " #%d: <%p>, %ps", idx, taddr, ACCESS_PRIVATE(timer->function));
         |                                                      ^
   2 errors generated.


vim +49 kernel/time/timer_list.c

    44	
    45	static void
    46	print_timer(struct seq_file *m, struct hrtimer *taddr, struct hrtimer *timer,
    47		    int idx, u64 now)
    48	{
  > 49		SEQ_printf(m, " #%d: <%p>, %ps", idx, taddr, ACCESS_PRIVATE(timer->function));
    50		SEQ_printf(m, ", S:%02x", timer->state);
    51		SEQ_printf(m, "\n");
    52		SEQ_printf(m, " # expires at %Lu-%Lu nsecs [in %Ld to %Ld nsecs]\n",
    53			(unsigned long long)ktime_to_ns(hrtimer_get_softexpires(timer)),
    54			(unsigned long long)ktime_to_ns(hrtimer_get_expires(timer)),
    55			(long long)(ktime_to_ns(hrtimer_get_softexpires(timer)) - now),
    56			(long long)(ktime_to_ns(hrtimer_get_expires(timer)) - now));
    57	}
    58	

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

             reply	other threads:[~2025-04-04 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 17:04 kernel test robot [this message]
2025-04-04 17:33 ` [tip:timers/cleanups 5/10] kernel/time/timer_list.c:49:77: error: too few arguments provided to function-like macro invocation Nam Cao

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=202504050045.fyyfMGEQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=namcao@linutronix.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@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