From: Jason Wang <jasowang@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, mst@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH V7 3/8] vringh: IOTLB support
Date: Wed, 25 Mar 2020 11:13:54 +0800 [thread overview]
Message-ID: <4032c9a2-a6c1-a041-fd59-81a8bf2fca46@redhat.com> (raw)
In-Reply-To: <202003250217.stptJTnJ%lkp@intel.com>
On 2020/3/25 上午2:19, kbuild test robot wrote:
> Hi Jason,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on vhost/linux-next]
> [also build test ERROR on linux/master linus/master v5.6-rc7 next-20200324]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/Jason-Wang/vDPA-support/20200324-142634
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> config: alpha-randconfig-a001-20200324 (attached as .config)
> compiler: alpha-linux-gcc (GCC) 9.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> GCC_VERSION=9.2.0 make.cross ARCH=alpha
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> alpha-linux-ld: drivers/vhost/vringh.o: in function `iotlb_translate':
> drivers/vhost/vringh.c:1079: undefined reference to `vhost_iotlb_itree_first'
This is because VHOST now depends on VHOST_IOTLB, but it was still
selected by MIC or VOP.
Will fix this by switching to use "depends on" fro MIC and VOP
Thanks.
>>> alpha-linux-ld: drivers/vhost/vringh.c:1079: undefined reference to `vhost_iotlb_itree_first'
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-03-25 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 4:14 [PATCH V7 0/8] vDPA support Jason Wang
2020-03-24 4:14 ` [PATCH V7 1/8] vhost: allow per device message handler Jason Wang
2020-03-24 4:14 ` [PATCH V7 2/8] vhost: factor out IOTLB Jason Wang
2020-03-24 4:14 ` [PATCH V7 3/8] vringh: IOTLB support Jason Wang
2020-03-24 18:19 ` kbuild test robot
2020-03-25 3:13 ` Jason Wang [this message]
2020-03-24 4:14 ` [PATCH V7 4/8] vDPA: introduce vDPA bus Jason Wang
2020-03-24 4:14 ` [PATCH V7 5/8] virtio: introduce a vDPA based transport Jason Wang
2020-03-24 4:14 ` [PATCH V7 6/8] vhost: introduce vDPA-based backend Jason Wang
2020-03-24 4:14 ` [PATCH V7 7/8] vdpasim: vDPA device simulator Jason Wang
2020-03-25 2:25 ` kbuild test robot
2020-03-25 8:15 ` Jason Wang
2020-03-24 4:14 ` [PATCH V7 8/8] virtio: Intel IFC VF driver for VDPA Jason Wang
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=4032c9a2-a6c1-a041-fd59-81a8bf2fca46@redhat.com \
--to=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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®