diff options
| author | Sylvain Trias <bozo@nobodix.org> | 2015-04-08 08:27:57 (GMT) |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2015-04-08 20:23:48 (GMT) |
| commit | 7a4580075d37d334b40f510cab54008d2dc66827 (patch) | |
| tree | 1db7ed0ebb7be47a7a1cdabebb66c77e42813e8e | |
| parent | c8a329c777f5a38e39b25425d29b2e37cbb06614 (diff) | |
| download | linux-7a4580075d37d334b40f510cab54008d2dc66827.tar.xz | |
Documentation/memory-barriers.txt: typo fix
Fix an obvious typo in the documentation.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
| -rw-r--r-- | Documentation/memory-barriers.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index ca2387e..a3a94ff 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -1711,7 +1711,7 @@ There are some more advanced barrier functions: } The dma_rmb() allows us guarantee the device has released ownership - before we read the data from the descriptor, and he dma_wmb() allows + before we read the data from the descriptor, and the dma_wmb() allows us to guarantee the data is written to the descriptor before the device can see it now has ownership. The wmb() is needed to guarantee that the cache coherent memory writes have completed before attempting a write to |