summaryrefslogtreecommitdiffstats
path: root/Documentation/block/barrier.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/block/barrier.txt')
-rw-r--r--Documentation/block/barrier.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/block/barrier.txt b/Documentation/block/barrier.txt
index 0397151..761073e 100644
--- a/Documentation/block/barrier.txt
+++ b/Documentation/block/barrier.txt
@@ -25,7 +25,7 @@ of the following three ways.
i. For devices which have queue depth greater than 1 (TCQ devices) and
support ordered tags, block layer can just issue the barrier as an
ordered request and the lower level driver, controller and drive
-itself are responsible for making sure that the ordering contraint is
+itself are responsible for making sure that the ordering constraint is
met. Most modern SCSI controllers/drives should support this.
NOTE: SCSI ordered tag isn't currently used due to limitation in the
OpenPOWER on IntegriCloud