From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2019.04.16a 71/72] ERROR: "sched_setaffinity" [kernel/rcu/rcutorture.ko] undefined!
Date: Tue, 23 Apr 2019 05:58:58 -0700 [thread overview]
Message-ID: <20190423125858.GI3923@linux.ibm.com> (raw)
In-Reply-To: <201904232031.O1MJPq0W%lkp@intel.com>
On Tue, Apr 23, 2019 at 08:19:33PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.04.16a
> head: ca8714f549be5a186d086a223184095759eb7094
> commit: 672c5761e6763a76b414a8deaebb787696100ea1 [71/72] rcutorture: Add trivial RCU implementation
> config: ia64-allmodconfig (attached as .config)
> compiler: ia64-linux-gcc (GCC) 8.1.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 672c5761e6763a76b414a8deaebb787696100ea1
> # save the attached .config to linux build tree
> GCC_VERSION=8.1.0 make.cross ARCH=ia64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "sched_setaffinity" [kernel/rcu/rcutorture.ko] undefined!
> ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!
> ERROR: "__sw_hweight8" [drivers/net/wireless/mediatek/mt76/mt7603/mt7603e.ko] undefined!
> ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined!
Good catch -- fixing this with the usual trampoline function.
Thanx, Paul
prev parent reply other threads:[~2019-04-23 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 12:19 [rcu:dev.2019.04.16a 71/72] ERROR: "sched_setaffinity" [kernel/rcu/rcutorture.ko] undefined! kbuild test robot
2019-04-23 12:58 ` Paul E. McKenney [this message]
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=20190423125858.GI3923@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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.