From: Jason Wang <jasowang@redhat.com>
To: Eli Cohen <eli@mellanox.com>,
mst@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: shahafs@mellanox.com, saeedm@mellanox.com, parav@mellanox.com
Subject: Re: [PATCH V2 vhost next 05/10] vhost: Fix documentation
Date: Tue, 21 Jul 2020 13:35:03 +0800 [thread overview]
Message-ID: <7c323cac-fa03-bc46-1c41-ee7d37f350cf@redhat.com> (raw)
In-Reply-To: <20200720071416.32112-6-eli@mellanox.com>
On 2020/7/20 下午3:14, Eli Cohen wrote:
> Fix documentation to match actual function prototypes.
>
> Reviewed-by: Parav Pandit <parav@mellanox.com>
> Signed-off-by: Eli Cohen <eli@mellanox.com>
Acked-by: Jason Wang <jasowang@redhat.com>
> ---
> drivers/vhost/iotlb.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vhost/iotlb.c b/drivers/vhost/iotlb.c
> index 1f0ca6e44410..0d4213a54a88 100644
> --- a/drivers/vhost/iotlb.c
> +++ b/drivers/vhost/iotlb.c
> @@ -149,7 +149,7 @@ EXPORT_SYMBOL_GPL(vhost_iotlb_free);
> * vhost_iotlb_itree_first - return the first overlapped range
> * @iotlb: the IOTLB
> * @start: start of IOVA range
> - * @end: end of IOVA range
> + * @last: last byte in IOVA range
> */
> struct vhost_iotlb_map *
> vhost_iotlb_itree_first(struct vhost_iotlb *iotlb, u64 start, u64 last)
> @@ -162,7 +162,7 @@ EXPORT_SYMBOL_GPL(vhost_iotlb_itree_first);
> * vhost_iotlb_itree_first - return the next overlapped range
> * @iotlb: the IOTLB
> * @start: start of IOVA range
> - * @end: end of IOVA range
> + * @last: last byte IOVA range
> */
> struct vhost_iotlb_map *
> vhost_iotlb_itree_next(struct vhost_iotlb_map *map, u64 start, u64 last)
next prev parent reply other threads:[~2020-07-21 5:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 7:14 [PATCH V2 vhost next 00/10] VDPA support for Mellanox ConnectX devices Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 01/10] vhost-vdpa: support batch updating Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 02/10] vdpa_sim: use the batching API Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 03/10] vdpa: remove hard coded virtq num Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 04/10] net/vdpa: Use struct for set/get vq state Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 05/10] vhost: Fix documentation Eli Cohen
2020-07-21 5:35 ` Jason Wang [this message]
2020-07-20 7:14 ` [PATCH V2 vhost next 06/10] vdpa: Modify get_vq_state() to return error code Eli Cohen
2020-07-21 5:34 ` Jason Wang
2020-07-20 7:14 ` [PATCH V2 vhost next 07/10] vdpa/mlx5: Add hardware descriptive header file Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 08/10] vdpa/mlx5: Add support library for mlx5 VDPA implementation Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 09/10] vdpa/mlx5: Add shared memory registration code Eli Cohen
2020-07-20 7:14 ` [PATCH V2 vhost next 10/10] vdpa/mlx5: Add VDPA driver for supported mlx5 devices Eli Cohen
2020-07-20 12:55 ` kernel test robot
2020-07-22 7:46 ` Eli Cohen
2020-07-21 3:30 ` kernel test robot
2020-07-21 5:51 ` Jason Wang
-- strict thread matches above, loose matches on Subject: below --
2020-07-20 6:54 [PATCH V2 vhost next 00/10] VDPA support for Mellanox ConnectX devices Eli Cohen
2020-07-20 6:54 ` [PATCH V2 vhost next 05/10] vhost: Fix documentation Eli Cohen
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=7c323cac-fa03-bc46-1c41-ee7d37f350cf@redhat.com \
--to=jasowang@redhat.com \
--cc=eli@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=saeedm@mellanox.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;
as well as URLs for NNTP newsgroup(s).