From: kbuild test robot <lkp@intel.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>,
mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jasowang@redhat.com
Cc: kbuild-all@lists.01.org, lulu@redhat.com, dan.daly@intel.com,
cunming.liang@intel.com, Zhu Lingshan <lingshan.zhu@intel.com>
Subject: [RFC PATCH] vdpa: vhost_vdpa_poll_stop() can be static
Date: Wed, 27 May 2020 17:16:46 +0800 [thread overview]
Message-ID: <20200527091646.GA80910@369e1fe990b8> (raw)
In-Reply-To: <1590471145-4436-1-git-send-email-lingshan.zhu@intel.com>
Signed-off-by: kbuild test robot <lkp@intel.com>
---
vdpa.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
index d3a2acafedecd4..5037ce7f48cd42 100644
--- a/drivers/vhost/vdpa.c
+++ b/drivers/vhost/vdpa.c
@@ -287,12 +287,12 @@ static long vhost_vdpa_get_vring_num(struct vhost_vdpa *v, u16 __user *argp)
return 0;
}
-void vhost_vdpa_poll_stop(struct vhost_virtqueue *vq)
+static void vhost_vdpa_poll_stop(struct vhost_virtqueue *vq)
{
vhost_poll_stop(&vq->poll);
}
-int vhost_vdpa_poll_start(struct vhost_virtqueue *vq)
+static int vhost_vdpa_poll_start(struct vhost_virtqueue *vq)
{
struct vhost_poll *poll = &vq->poll;
struct file *file = vq->kick;
@@ -747,7 +747,7 @@ static int vhost_vdpa_poll_worker(wait_queue_entry_t *wait, unsigned int mode,
return 0;
}
-void vhost_vdpa_poll_init(struct vhost_dev *dev)
+static void vhost_vdpa_poll_init(struct vhost_dev *dev)
{
struct vhost_virtqueue *vq;
struct vhost_poll *poll;
next prev parent reply other threads:[~2020-05-27 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 5:32 [PATCH] vdpa: bypass waking up vhost_woker for vdpa vq kick Zhu Lingshan
2020-05-26 22:53 ` kbuild test robot
2020-05-27 9:16 ` kbuild test robot [this message]
2020-05-28 10:06 ` Jason Wang
2020-06-02 9:42 ` Dan Carpenter
2020-06-02 10:16 ` Jason Wang
2020-06-02 11:10 ` 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=20200527091646.GA80910@369e1fe990b8 \
--to=lkp@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.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;
as well as URLs for NNTP newsgroup(s).