[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <276972d5-ee01-9c4a-d3cc-0db4d0dd2b7b@redhat.com>
Date: Tue, 15 Nov 2016 11:21:48 +0800
From: Jason Wang <jasowang@...hat.com>
To: Felipe Franciosi <felipe@...anix.com>,
"Michael S. Tsirkin" <mst@...hat.com>
Cc: virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] virtio_ring: fix description of virtqueue_get_buf
On 2016年11月14日 22:16, Felipe Franciosi wrote:
> The device (not the driver) populates the used ring and includes the len
> of how much data was written.
>
> Signed-off-by: Felipe Franciosi <felipe@...anix.com>
> ---
> drivers/virtio/virtio_ring.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> index 489bfc6..8a0d6a9 100644
> --- a/drivers/virtio/virtio_ring.c
> +++ b/drivers/virtio/virtio_ring.c
> @@ -649,7 +649,7 @@ static inline bool more_used(const struct vring_virtqueue *vq)
> * @vq: the struct virtqueue we're talking about.
> * @len: the length written into the buffer
> *
> - * If the driver wrote data into the buffer, @len will be set to the
> + * If the device wrote data into the buffer, @len will be set to the
> * amount written. This means you don't need to clear the buffer
> * beforehand to ensure there's no data leakage in the case of short
> * writes.
Reviewed-by: Jason Wang <jasowang@...hat.com>
Powered by blists - more mailing lists