From: kbuild test robot <lkp@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org, Julia Lawall <Julia.Lawall@lip6.fr>,
Yongji Xie <xyjxie@linux.vnet.ibm.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Feng Wu <feng.wu@intel.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 2/2] vfio: add virtio pci quirk
Date: Tue, 30 Aug 2016 17:59:06 +0800 [thread overview]
Message-ID: <201608301736.udJsgwY2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472523968-9540-3-git-send-email-mst@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hi Michael,
[auto build test ERROR on vfio/next]
[also build test ERROR on v4.8-rc4 next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Michael-S-Tsirkin/vfio-blacklist-legacy-virtio-devices/20160830-124010
base: https://github.com/awilliam/linux-vfio.git next
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "vfio_is_noiommu_group_dev" [drivers/vfio/pci/vfio-pci.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 37603 bytes --]
next prev parent reply other threads:[~2016-08-30 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 2:27 [PATCH v2 0/2] vfio: blacklist legacy virtio devices Michael S. Tsirkin
2016-08-30 2:27 ` [PATCH v2 1/2] vfio: report group noiommu status Michael S. Tsirkin
2016-08-30 2:27 ` [PATCH v2 2/2] vfio: add virtio pci quirk Michael S. Tsirkin
2016-08-30 3:23 ` Alex Williamson
2016-08-30 3:48 ` Michael S. Tsirkin
2016-08-30 3:52 ` Alex Williamson
2016-08-30 3:57 ` Michael S. Tsirkin
2016-08-30 4:53 ` Alex Williamson
2016-08-30 5:20 ` Michael S. Tsirkin
2016-08-30 12:46 ` Alex Williamson
2016-08-30 9:59 ` kbuild test robot [this message]
2016-08-30 3:16 ` [Qemu-devel] [PATCH v2 0/2] vfio: blacklist legacy virtio devices Jason Wang
2016-08-30 3:49 ` Michael S. Tsirkin
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=201608301736.udJsgwY2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=alex.williamson@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=feng.wu@intel.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xyjxie@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).