summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShuah Khan <shuah.khan@hp.com>2013-02-28 01:03:10 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-28 03:10:11 (GMT)
commitbe62bc410061778134c2b3b3dd93f51bb5acc839 (patch)
tree6139759d3cba204515c90fecc51d371fb1b40695
parentb88a105802e9aeb6e234e8106659f5d1271081bb (diff)
downloadlinux-be62bc410061778134c2b3b3dd93f51bb5acc839.tar.xz
Documentation/DMA-API-HOWTO.txt: minor grammar corrections
Signed-off-by: Shuah Khan <shuah.khan@hp.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--Documentation/DMA-API-HOWTO.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
index 4a4fb29..65470ca 100644
--- a/Documentation/DMA-API-HOWTO.txt
+++ b/Documentation/DMA-API-HOWTO.txt
@@ -488,9 +488,10 @@ will invoke the generic mapping error check interface. Doing so will ensure
that the mapping code will work correctly on all dma implementations without
any dependency on the specifics of the underlying implementation. Using the
returned address without checking for errors could result in failures ranging
-from panics to silent data corruption. Couple of example of incorrect ways to
-check for errors that make assumptions about the underlying dma implementation
-are as follows and these are applicable to dma_map_page() as well.
+from panics to silent data corruption. A couple of examples of incorrect ways
+to check for errors that make assumptions about the underlying dma
+implementation are as follows and these are applicable to dma_map_page() as
+well.
Incorrect example 1:
dma_addr_t dma_handle;