From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [linux-next:master 12118/13934] config.c:undefined reference to `mach_get_rtc_pll'
Date: Mon, 23 May 2022 21:47:34 +0800 [thread overview]
Message-ID: <202205232103.zOPlZ3yo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cc63e8e92cb872081f249ea16e6c460642f3e4fb
commit: 94cac569012aff092b029f0d674f9ab944b08b5a [12118/13934] m68knommu: fix undefined reference to `mach_get_rtc_pll'
config: m68k-randconfig-r011-20220522 (https://download.01.org/0day-ci/archive/20220523/202205232103.zOPlZ3yo-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.3.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=94cac569012aff092b029f0d674f9ab944b08b5a
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 94cac569012aff092b029f0d674f9ab944b08b5a
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
m68k-linux-ld: arch/m68k/q40/config.o: in function `config_q40':
>> config.c:(.init.text+0xf2): undefined reference to `mach_get_rtc_pll'
>> m68k-linux-ld: config.c:(.init.text+0xfc): undefined reference to `mach_set_rtc_pll'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-23 13:48 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=202205232103.zOPlZ3yo-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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