From: kernel test robot <lkp@intel.com>
To: Stephen Eta Zhou <stephen.eta.zhou@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
groeck7@gmail.com, Stephen Eta Zhou <stephen.eta.zhou@gmail.com>
Subject: Re: [PATCH] clocksource: timer-sp804: Fix an Oops when read_current_timer is called on ARM32 platforms where the SP804 is not registered as the sched_clock.
Date: Thu, 25 Dec 2025 06:05:16 +0800 [thread overview]
Message-ID: <202512250520.APOMkYRQ-lkp@intel.com> (raw)
In-Reply-To: <20251219-fix_timersp804-v1-1-020e3cde7cf5@gmail.com>
Hi Stephen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8f0b4cce4481fb22653697cced8d0d04027cb1e8]
url: https://github.com/intel-lab-lkp/linux/commits/Stephen-Eta-Zhou/clocksource-timer-sp804-Fix-an-Oops-when-read_current_timer-is-called-on-ARM32-platforms-where-the-SP804-is-not-register/20251219-130527
base: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
patch link: https://lore.kernel.org/r/20251219-fix_timersp804-v1-1-020e3cde7cf5%40gmail.com
patch subject: [PATCH] clocksource: timer-sp804: Fix an Oops when read_current_timer is called on ARM32 platforms where the SP804 is not registered as the sched_clock.
config: arm-randconfig-r134-20251224 (https://download.01.org/0day-ci/archive/20251225/202512250520.APOMkYRQ-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 4ef602d446057dabf5f61fb221669ecbeda49279)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251225/202512250520.APOMkYRQ-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/202512250520.APOMkYRQ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/clocksource/timer-sp804.c:112:21: sparse: sparse: symbol 'delay_clkevt' was not declared. Should it be static?
vim +/delay_clkevt +112 drivers/clocksource/timer-sp804.c
108
109 /* Register delay timer backed by the hardware counter */
110 #ifdef CONFIG_ARM
111 static struct delay_timer delay;
> 112 struct sp804_clkevt *delay_clkevt;
113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-24 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 4:59 Stephen Eta Zhou
2025-12-24 22:05 ` kernel test robot [this message]
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=202512250520.APOMkYRQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=groeck7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stephen.eta.zhou@gmail.com \
--cc=tglx@linutronix.de \
/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®