From: kernel test robot <lkp@intel.com>
To: "Jason A. Donenfeld" <zx2c4@kernel.org>
Cc: kbuild-all@lists.01.org, build@wireguard.com,
linux-kernel@vger.kernel.org
Subject: [zx2c4-wireguard:jd/new-archs 1/3] ERROR: modpost: "schedule_hrtimeout_range_clock" [drivers/net/wireguard/wireguard.ko] undefined!
Date: Thu, 21 Jul 2022 21:13:47 +0800 [thread overview]
Message-ID: <202207212115.Dutn6aMv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/wireguard-linux.git jd/new-archs
head: 627fef82b5cfcb865fd8cf67d2d18f17c8c2b2a2
commit: 82c472126eb825e1e5ed42599a5e78fd69eac274 [1/3] wireguard: ratelimiter: use hrtimer in selftest
config: microblaze-randconfig-r012-20220718 (https://download.01.org/0day-ci/archive/20220721/202207212115.Dutn6aMv-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.1.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/zx2c4/wireguard-linux.git/commit/?id=82c472126eb825e1e5ed42599a5e78fd69eac274
git remote add zx2c4-wireguard https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/wireguard-linux.git
git fetch --no-tags zx2c4-wireguard jd/new-archs
git checkout 82c472126eb825e1e5ed42599a5e78fd69eac274
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze 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 >>, old ones prefixed by <<):
>> ERROR: modpost: "schedule_hrtimeout_range_clock" [drivers/net/wireguard/wireguard.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-21 13:14 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=202207212115.Dutn6aMv-lkp@intel.com \
--to=lkp@intel.com \
--cc=build@wireguard.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zx2c4@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®