From: kernel test robot <lkp@intel.com>
To: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, rob.miller@broadcom.com,
lingshan.zhu@intel.com, eperezma@redhat.com, lulu@redhat.com,
shahafs@mellanox.com, hanand@xilinx.com, mhabets@solarflare.com
Subject: [RFC PATCH] vdpa_sim: vdpasim_get_iova_range() can be static
Date: Fri, 21 Aug 2020 20:20:51 +0800 [thread overview]
Message-ID: <20200821122051.GA60229@ff58d72860ac> (raw)
In-Reply-To: <20200821092813.8952-4-jasowang@redhat.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
vdpa_sim.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c b/drivers/vdpa/vdpa_sim/vdpa_sim.c
index 89854e17c3c27b..ff6c9fd8d879bd 100644
--- a/drivers/vdpa/vdpa_sim/vdpa_sim.c
+++ b/drivers/vdpa/vdpa_sim/vdpa_sim.c
@@ -574,7 +574,7 @@ static u32 vdpasim_get_generation(struct vdpa_device *vdpa)
return vdpasim->generation;
}
-struct vdpa_iova_range vdpasim_get_iova_range(struct vdpa_device *vdpa)
+static struct vdpa_iova_range vdpasim_get_iova_range(struct vdpa_device *vdpa)
{
struct vdpa_iova_range range = {
.first = 0ULL,
next prev parent reply other threads:[~2020-08-21 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 9:28 [PATCH V2 0/3] vDPA: API for reporting IOVA range Jason Wang
2020-08-21 9:28 ` [PATCH V2 1/3] vdpa: introduce config op to get valid iova range Jason Wang
2020-08-21 9:28 ` [PATCH V2 2/3] vhost: vdpa: report " Jason Wang
2020-08-23 6:40 ` Eli Cohen
2020-08-31 8:38 ` Jason Wang
2020-08-21 9:28 ` [PATCH V2 3/3] vdpa_sim: implement get_iova_range() Jason Wang
2020-08-21 10:33 ` kernel test robot
2020-08-21 12:20 ` kernel test robot
2020-08-21 12:20 ` kernel test robot [this message]
2020-08-21 12:51 ` kernel test robot
2020-08-21 12:59 ` kernel 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=20200821122051.GA60229@ff58d72860ac \
--to=lkp@intel.com \
--cc=eperezma@redhat.com \
--cc=hanand@xilinx.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=rob.miller@broadcom.com \
--cc=shahafs@mellanox.com \
--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