From 83e2126994d4bafc7269bdc123a4fb06c78ccc4d Mon Sep 17 00:00:00 2001
From: rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>
Date: Mon, 10 Feb 2014 10:30:24 +0000
Subject: patch feedback-4.patch

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@214 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
---
 content.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'content.tex')

diff --git a/content.tex b/content.tex
index 9713817..7e77740 100644
--- a/content.tex
+++ b/content.tex
@@ -424,7 +424,7 @@ written by the driver and read by the device.
 The “idx” field indicates where the driver would put the next descriptor
 entry in the ring (modulo the queue size). This starts at 0, and increases.
 
-If the VIRTIO_RING_F_INDIRECT_DESC feature bit is not negotiated, the
+If the VIRTIO_RING_F_EVENT_IDX feature bit is not negotiated, the
 “flags” field offers a crude interrupt control mechanism.  The driver
 MUST set this to 0 or 1: 1 indicates that the device SHOULD NOT send
 an interrupt when it consumes a descriptor chain from the available
@@ -474,7 +474,7 @@ for drivers using untrusted buffers: if you do not know exactly
 how much has been written by the device, you usually have to zero
 the buffer to ensure no data leakage occurs.
 
-If the VIRTIO_RING_F_INDIRECT_DESC feature bit is not negotiated, the
+If the VIRTIO_RING_F_EVENT_IDX feature bit is not negotiated, the
 “flags” field offers a crude interrupt control mechanism.  The driver
 MUST initialize this to 0, the device MUST set this to 0 or 1: 1
 indicates that the driver SHOULD NOT send an notification when it adds
-- 
cgit v1.2.3

