From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [tglx-devel:timers/cleanup 49/59] arch/mips/bcm63xx/cpu.c:303:10: error: implicit declaration of function 'current_cpu_type'; did you mean 'current_cpu_data'?
Date: Mon, 13 Jul 2026 11:22:50 +0800 [thread overview]
Message-ID: <202607131002.CFOusS91-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git timers/cleanup
head: 0ad363c8e014568032d53fe2c7ab288de68373f4
commit: dc057dc5f95cb914748472aedcb49ebc5953debf [49/59] mips: Select ARCH_HAS_RANDOM_ENTROPY
config: mips-randconfig-r073-20260713 (https://download.01.org/0day-ci/archive/20260713/202607131002.CFOusS91-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 8.5.0
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260713/202607131002.CFOusS91-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/202607131002.CFOusS91-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/mips/bcm63xx/cpu.c: In function 'bcm63xx_cpu_init':
>> arch/mips/bcm63xx/cpu.c:303:10: error: implicit declaration of function 'current_cpu_type'; did you mean 'current_cpu_data'? [-Werror=implicit-function-declaration]
switch (current_cpu_type()) {
^~~~~~~~~~~~~~~~
current_cpu_data
cc1: some warnings being treated as errors
vim +303 arch/mips/bcm63xx/cpu.c
e7300d04bd0809 Maxime Bizon 2009-08-18 293
e7300d04bd0809 Maxime Bizon 2009-08-18 294 void __init bcm63xx_cpu_init(void)
e7300d04bd0809 Maxime Bizon 2009-08-18 295 {
13be798c57ebe5 Jonas Gorski 2013-03-21 296 unsigned int tmp;
2b5b9b786c177f Florian Fainelli 2009-10-14 297 unsigned int cpu = smp_processor_id();
13be798c57ebe5 Jonas Gorski 2013-03-21 298 u32 chipid_reg;
e7300d04bd0809 Maxime Bizon 2009-08-18 299
e7300d04bd0809 Maxime Bizon 2009-08-18 300 /* soc registers location depends on cpu type */
13be798c57ebe5 Jonas Gorski 2013-03-21 301 chipid_reg = 0;
e7300d04bd0809 Maxime Bizon 2009-08-18 302
d7b12056bc9cbd Wu Zhangjin 2010-12-26 @303 switch (current_cpu_type()) {
:::::: The code at line 303 was first introduced by commit
:::::: d7b12056bc9cbd7f0c0ae5bc52f2b049d48c4314 MIPS: Use current_cpu_type() instead of c->cputype
:::::: TO: Wu Zhangjin <wuzhangjin@gmail.com>
:::::: CC: Ralf Baechle <ralf@linux-mips.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-13 3:23 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=202607131002.CFOusS91-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@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 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.