From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/vdso-alarm-clocks 3/5] kernel/time/alarmtimer.c:105:undefined reference to `vdso_time_enable_alarmclock'
Date: Fri, 16 Oct 2026 10:55:07 +0200 [thread overview]
Message-ID: <202610161018.bTkFTUke-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/vdso-alarm-clocks
head: c8bb37f3267c7cbf3aed873255994d37a43122c9
commit: 16c670855b6263e33441b6502dd778778a33ae69 [3/5] vdso: Add alarmclock support infrastructure
config: csky-randconfig-r2200-20261016 (https://download.01.org/0day-ci/archive/20261016/202610161018.bTkFTUke-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.3.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261016/202610161018.bTkFTUke-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/202610161018.bTkFTUke-lkp@intel.com/
All errors (new ones prefixed by >>):
csky-linux-ld: kernel/time/alarmtimer.o: in function `alarmtimer_rtc_add_device':
>> kernel/time/alarmtimer.c:105:(.text+0x8f0): undefined reference to `vdso_time_enable_alarmclock'
csky-linux-ld: kernel/time/alarmtimer.o: in function `__srcu_read_lock':
>> include/linux/srcutiny.h:90:(.text+0x9a8): undefined reference to `vdso_time_enable_alarmclock'
vim +105 kernel/time/alarmtimer.c
82
83 static int alarmtimer_rtc_add_device(struct device *dev)
84 {
85 struct rtc_device *rtc = to_rtc_device(dev);
86 struct platform_device *pdev;
87 int ret = 0;
88
89 if (rtcdev)
90 return -EBUSY;
91
92 if (!test_bit(RTC_FEATURE_ALARM, rtc->features))
93 return -1;
94 if (!device_may_wakeup(rtc->dev.parent))
95 return -1;
96
97 pdev = platform_device_register_data(dev, "alarmtimer",
98 PLATFORM_DEVID_AUTO, NULL, 0);
99 if (!IS_ERR(pdev))
100 device_init_wakeup(&pdev->dev, true);
101
102 scoped_guard(spinlock_irqsave, &rtcdev_lock) {
103 if (!IS_ERR(pdev) && !rtcdev && try_module_get(rtc->owner)) {
104 rtcdev = rtc;
> 105 vdso_time_enable_alarmclock();
106 /* hold a reference so it doesn't go away */
107 get_device(dev);
108 pdev = NULL;
109 } else {
110 ret = -1;
111 }
112 }
113
114 platform_device_unregister(pdev);
115 return ret;
116 }
117
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-16 8:55 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=202610161018.bTkFTUke-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux@weissschuh.net \
--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 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.