From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Sudeep Dutt <sudeep.dutt@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: ERROR: "vring_del_virtqueue" [drivers/misc/mic/vop/vop.ko] undefined!
Date: Sat, 30 Apr 2016 09:49:01 -0700 [thread overview]
Message-ID: <5724E1FD.4060906@infradead.org> (raw)
In-Reply-To: <201604182306.Y6JK1v8n%fengguang.wu@intel.com>
On 04/18/16 08:05, kbuild test robot wrote:
> Hi Sudeep,
>
> FYI, the error/warning still remains.
and still happens in linux-next-20160428...
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: c3b46c73264b03000d1e18b22f5caf63332547c9
> commit: 8810df37762746657cfe84014a8f30758e8f366a misc: mic: Enable VOP debugfs and driver build
> date: 10 weeks ago
> config: x86_64-randconfig-s2-04182146 (attached as .config)
> reproduce:
> git checkout 8810df37762746657cfe84014a8f30758e8f366a
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "vring_del_virtqueue" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "register_virtio_device" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "unregister_virtio_device" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "vring_new_virtqueue" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "virtio_config_changed" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "vring_interrupt" [drivers/misc/mic/vop/vop.ko] undefined!
>>> ERROR: "vring_transport_features" [drivers/misc/mic/vop/vop.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
--
~Randy
next prev parent reply other threads:[~2016-04-30 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 15:05 ERROR: "vring_del_virtqueue" [drivers/misc/mic/vop/vop.ko] undefined! kbuild test robot
2016-04-30 16:49 ` Randy Dunlap [this message]
2016-04-30 18:56 ` Sudeep Dutt
2016-04-30 20:06 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2016-04-03 13:50 kbuild test robot
2016-03-22 20:21 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=5724E1FD.4060906@infradead.org \
--to=rdunlap@infradead.org \
--cc=ashutosh.dixit@intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.dutt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox