summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorFelipe Franciosi <felipe@nutanix.com>2016-11-14 06:16:15 -0800
committerMichael S. Tsirkin <mst@redhat.com>2016-12-16 00:13:38 +0200
commit0c7eaf5930e145b9f1a0121bd5813a05b0fc77f2 (patch)
treefc9c8a484088dc9d8c4589e19ab1f8c2c235ef96 /drivers
parentb9fd06d0dae38a88efa4b770dfa9db7dcbe3cda9 (diff)
virtio_ring: fix description of virtqueue_get_buf
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@nutanix.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/virtio/virtio_ring.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index d2863c321e93..409aeaa49246 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.