From: Robin Murphy <robin.murphy@arm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!
Date: Thu, 1 Mar 2018 16:25:45 +0000 [thread overview]
Message-ID: <a7358051-b4a0-c07c-1747-f4702abf220f@arm.com> (raw)
In-Reply-To: <201803011134.bk1IHi9I%fengguang.wu@intel.com>
On 01/03/18 03:18, kbuild test robot wrote:
> Hi Robin,
>
> First bad commit (maybe != root cause):
I have to admit I'm slightly intrigued how this commit could possibly
appear relevant to the IA64 build at all, let alone to this error :/
Robin.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 97ace515f01439d4cf6e898b4094040dc12d36e7
> commit: e1a50de37860b3a93a9d643b09638db5aff47650 arm64: cputype: Silence Sparse warnings
> date: 12 days ago
> config: ia64-allmodconfig (attached as .config)
> compiler: ia64-linux-gcc (GCC) 7.2.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 e1a50de37860b3a93a9d643b09638db5aff47650
> # save the attached .config to linux build tree
> make.cross ARCH=ia64
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!
> ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2018-03-01 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 3:18 kbuild test robot
2018-03-01 16:25 ` Robin Murphy [this message]
2018-03-03 1:56 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2017-05-07 1:38 kbuild test robot
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=a7358051-b4a0-c07c-1747-f4702abf220f@arm.com \
--to=robin.murphy@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.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®