aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShuah Khan <shuah.khan@hp.com>2013-02-27 20:03:10 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-27 22:10:11 -0500
commitbe62bc410061778134c2b3b3dd93f51bb5acc839 (patch)
tree6139759d3cba204515c90fecc51d371fb1b40695
parentb88a105802e9aeb6e234e8106659f5d1271081bb (diff)
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 4a4fb295ceef..65470cae471d 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
488that the mapping code will work correctly on all dma implementations without 488that the mapping code will work correctly on all dma implementations without
489any dependency on the specifics of the underlying implementation. Using the 489any dependency on the specifics of the underlying implementation. Using the
490returned address without checking for errors could result in failures ranging 490returned address without checking for errors could result in failures ranging
491from panics to silent data corruption. Couple of example of incorrect ways to 491from panics to silent data corruption. A couple of examples of incorrect ways
492check for errors that make assumptions about the underlying dma implementation 492to check for errors that make assumptions about the underlying dma
493are as follows and these are applicable to dma_map_page() as well. 493implementation are as follows and these are applicable to dma_map_page() as
494well.
494 495
495Incorrect example 1: 496Incorrect example 1:
496 dma_addr_t dma_handle; 497 dma_addr_t dma_handle;