From: kernel test robot <lkp@intel.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Thomas Gleixner" <tglx@kernel.org>,
"Thomas Weißschuh " <thomas.weissschuh@linutronix.de>
Subject: [tip:timers/vdso 4/4] arch/sparc/include/uapi/../../../../lib/vdso/gettimeofday.c:288:24: error: call to undeclared function 'BITS_PER_TYPE'; ISO C99 and later do not support implicit function declarations
Date: Wed, 30 Sep 2026 16:14:46 +0800 [thread overview]
Message-ID: <202609301648.OQYqz8q1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/vdso
head: ca46a07c4b68246c4e400ce3649ab7228a878d8f
commit: ca46a07c4b68246c4e400ce3649ab7228a878d8f [4/4] vdso/gettimeofday: Assert that the clockid fits into the u32 bitmask
config: sparc64-defconfig (https://download.01.org/0day-ci/archive/20260930/202609301648.OQYqz8q1-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 5f609f950d2e80addf5566623013db68394334db)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260930/202609301648.OQYqz8q1-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/202609301648.OQYqz8q1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/sparc/vdso/vclock_gettime.c:22:
>> arch/sparc/include/uapi/../../../../lib/vdso/gettimeofday.c:288:24: error: call to undeclared function 'BITS_PER_TYPE'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
288 | BUILD_BUG_ON(clock >= BITS_PER_TYPE(msk));
| ^
1 error generated.
vim +/BITS_PER_TYPE +288 arch/sparc/include/uapi/../../../../lib/vdso/gettimeofday.c
273
274 static __always_inline bool
275 __cvdso_clock_gettime_common(const struct vdso_time_data *vd, clockid_t clock,
276 struct __kernel_timespec *ts)
277 {
278 const struct vdso_clock *vc = vd->clock_data;
279 u32 msk;
280
281 if (!vdso_clockid_valid(clock))
282 return false;
283
284 /*
285 * Convert the clockid to a bitmask and use it to check which
286 * clocks are handled in the VDSO directly.
287 */
> 288 BUILD_BUG_ON(clock >= BITS_PER_TYPE(msk));
289 msk = 1U << clock;
290 if (likely(msk & VDSO_HRES))
291 vc = &vc[CS_HRES_COARSE];
292 else if (msk & VDSO_COARSE)
293 return do_coarse(vd, &vc[CS_HRES_COARSE], clock, ts);
294 else if (msk & VDSO_RAW)
295 vc = &vc[CS_RAW];
296 else if (msk & VDSO_AUX)
297 return do_aux(vd, clock, ts);
298 else
299 return false;
300
301 return do_hres(vd, vc, clock, ts);
302 }
303
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-30 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 8:14 kernel test robot [this message]
2026-09-30 9:42 kernel test robot
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=202609301648.OQYqz8q1-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=x86@kernel.org \
--cc=zhanxusheng1024@gmail.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
all inboxes | Powered by JetHome®