From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 5610/6165] arch/mips/mm/cache.c:209:undefined reference to `r3k_cache_init'
Date: Fri, 8 Dec 2023 19:55:26 +0800 [thread overview]
Message-ID: <202312081904.NkusJJO0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bc63de6e6ba0b16652c5fb4b9c9916b9e7ca1f23
commit: 13446ee48dac9ce1ef935cbe140534146a0a69a0 [5610/6165] mips: move cache declarations into header
config: mips-randconfig-r021-20230212 (https://download.01.org/0day-ci/archive/20231208/202312081904.NkusJJO0-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231208/202312081904.NkusJJO0-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/202312081904.NkusJJO0-lkp@intel.com/
All errors (new ones prefixed by >>):
mips64-linux-ld: arch/mips/mm/cache.o: in function `cpu_cache_init':
>> arch/mips/mm/cache.c:209:(.text+0x690): undefined reference to `r3k_cache_init'
vim +209 arch/mips/mm/cache.c
ed2adb74217a40 Thomas Bogendoerfer 2020-11-13 205
078a55fc824c16 Paul Gortmaker 2013-06-18 206 void cpu_cache_init(void)
^1da177e4c3f41 Linus Torvalds 2005-04-16 207 {
02cf2119684e52 Ralf Baechle 2005-10-01 208 if (cpu_has_3k_cache) {
02cf2119684e52 Ralf Baechle 2005-10-01 @209 r3k_cache_init();
:::::: The code at line 209 was first introduced by commit
:::::: 02cf2119684e52e97a8a90bd7630386e0f1a250a Cleanup the mess in cpu_cache_init.
:::::: TO: Ralf Baechle <ralf@linux-mips.org>
:::::: CC: Ralf Baechle <ralf@linux-mips.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-08 11:56 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=202312081904.NkusJJO0-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox