From: Jason Wang <jasowang@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
wexu@redhat.com, tiwei.bie@intel.com, maxime.coquelin@redhat.com,
jfreimann@redhat.com
Subject: Re: [PATCH net-next 1/8] vhost: move get_rx_bufs to vhost.c
Date: Wed, 4 Jul 2018 11:28:28 +0800 [thread overview]
Message-ID: <7183970a-4b1f-6322-2516-ea252375fe47@redhat.com> (raw)
In-Reply-To: <201807040813.LULqRH8c%fengguang.wu@intel.com>
On 2018年07月04日 09:01, kbuild test robot wrote:
> Hi Jason,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on net-next/master]
>
> url:https://github.com/0day-ci/linux/commits/Jason-Wang/Packed-virtqueue-for-vhost/20180703-154751
> config: x86_64-randconfig-s0-07032254 (attached as .config)
> compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> Note: the linux-review/Jason-Wang/Packed-virtqueue-for-vhost/20180703-154751 HEAD 01b902f1126212ea2597e6d09802bd9c4431bf82 builds fine.
> It only hurts bisectibility.
>
> All errors (new ones prefixed by >>):
>
> drivers//vhost/net.c: In function 'handle_rx':
>>> drivers//vhost/net.c:738:15: error: implicit declaration of function 'get_rx_bufs' [-Werror=implicit-function-declaration]
> headcount = get_rx_bufs(vq, vq->heads + nvq->done_idx,
> ^~~~~~~~~~~
> cc1: some warnings being treated as errors
>
> vim +/get_rx_bufs +738 drivers//vhost/net.c
My bad, forget to do one by one compling test.
Will post V2.
Thanks
next prev parent reply other threads:[~2018-07-04 3:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 5:37 [PATCH net-next 0/8] Packed virtqueue for vhost Jason Wang
2018-07-03 5:37 ` [PATCH net-next 1/8] vhost: move get_rx_bufs to vhost.c Jason Wang
2018-07-04 1:01 ` kbuild test robot
2018-07-04 3:28 ` Jason Wang [this message]
2018-07-03 5:37 ` [PATCH net-next 2/8] vhost: hide used ring layout from device Jason Wang
2018-07-03 5:37 ` [PATCH net-next 3/8] vhost: do not use vring_used_elem Jason Wang
2018-07-03 5:38 ` [PATCH net-next 4/8] vhost_net: do not explicitly manipulate vhost_used_elem Jason Wang
2018-07-03 5:38 ` [PATCH net-next 5/8] vhost: vhost_put_user() can accept metadata type Jason Wang
2018-07-03 5:38 ` [PATCH net-next 6/8] virtio: introduce packed ring defines Jason Wang
2018-07-04 4:48 ` Tiwei Bie
2018-07-04 5:26 ` Jason Wang
2018-07-04 20:15 ` Maxime Coquelin
2018-07-05 11:30 ` Jason Wang
2018-07-03 5:38 ` [PATCH net-next 7/8] vhost: packed ring support Jason Wang
2018-07-03 5:38 ` [PATCH net-next 8/8] vhost: event suppression for packed ring Jason Wang
2018-07-04 4:13 ` Wei Xu
2018-07-04 5:23 ` Jason Wang
2018-07-04 8:13 ` Wei Xu
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=7183970a-4b1f-6322-2516-ea252375fe47@redhat.com \
--to=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tiwei.bie@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.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