mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [mingo-tip:sched/headers 1839/2324] arch/mips/ath25/devices.h:36:10: error: implicit declaration of function 'smp_processor_id'
Date: Wed, 23 Feb 2022 11:27:44 +0800	[thread overview]
Message-ID: <202202231135.jSEszXqu-lkp@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git sched/headers
head:   7d9efc989eceed6a8fa475a186880ec4a1ad54a3
commit: 03d4ee3eff69c2a68c1717afc5a08d1142af6a57 [1839/2324] headers/deps: mm: Optimize <linux/node.h> dependencies
config: mips-ath25_defconfig (https://download.01.org/0day-ci/archive/20220223/202202231135.jSEszXqu-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git/commit/?id=03d4ee3eff69c2a68c1717afc5a08d1142af6a57
        git remote add mingo-tip git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
        git fetch --no-tags mingo-tip sched/headers
        git checkout 03d4ee3eff69c2a68c1717afc5a08d1142af6a57
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from arch/mips/ath25/early_printk.c:14:
>> arch/mips/ath25/devices.h:36:10: error: implicit declaration of function 'smp_processor_id' [-Werror,-Wimplicit-function-declaration]
           return (current_cpu_data.cputype == CPU_4KEC);
                   ^
   arch/mips/include/asm/cpu-info.h:120:35: note: expanded from macro 'current_cpu_data'
   #define current_cpu_data cpu_data[smp_processor_id()]
                                     ^
   1 error generated.


vim +/smp_processor_id +36 arch/mips/ath25/devices.h

1ac91b1f686e9d Sergey Ryazanov 2014-10-29  33  
43cc739fd98b8c Sergey Ryazanov 2014-10-29  34  static inline bool is_ar2315(void)
43cc739fd98b8c Sergey Ryazanov 2014-10-29  35  {
43cc739fd98b8c Sergey Ryazanov 2014-10-29 @36  	return (current_cpu_data.cputype == CPU_4KEC);
43cc739fd98b8c Sergey Ryazanov 2014-10-29  37  }
43cc739fd98b8c Sergey Ryazanov 2014-10-29  38  

:::::: The code at line 36 was first introduced by commit
:::::: 43cc739fd98b8c517ad45756d869f866e746ba04 MIPS: ath25: add common parts

:::::: TO: Sergey Ryazanov <ryazanov.s.a@gmail.com>
:::::: CC: Ralf Baechle <ralf@linux-mips.org>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

                 reply	other threads:[~2022-02-23  3:28 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=202202231135.jSEszXqu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@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

all inboxes | Powered by JetHome®