From a2503484f0579b0b6547c36207c0381a7eee2a4d Mon Sep 17 00:00:00 2001
From: pbonzini <pbonzini@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>
Date: Tue, 17 Jun 2014 13:12:30 +0000
Subject: content.tex: VIRTIO-106: mention possibility of failing TMFs

This completes the review of virtio-scsi based on observations
from Google.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

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

(limited to 'content.tex')

diff --git a/content.tex b/content.tex
index 56f58fa..e81636c 100644
--- a/content.tex
+++ b/content.tex
@@ -4811,9 +4811,9 @@ struct virtio_scsi_ctrl_tmf
   Similarly, the device MUST complete the selected commands (possibly
   with a VIRTIO_SCSI_S_ABORTED response code) upon receiving an "abort
   task" or "abort task set" TMF.  Such effects MUST take place before
-  the TMF itself is completed, and the device MUST use memory barriers
-  appropriately in order to ensure that the driver sees these writes
-  in the correct order.
+  the TMF itself is successfully completed, and the device MUST use
+  memory barriers appropriately in order to ensure that the driver sees
+  these writes in the correct order.
 
 \item Asynchronous notification query.
 \begin{lstlisting}
-- 
cgit v1.2.3

