From eff4a7ec8abf87f512480607d71d4c1298c9f171 Mon Sep 17 00:00:00 2001 From: Shuah Khan Date: Wed, 27 Feb 2013 17:03:10 -0800 Subject: [PATCH] --- yaml --- r: 359285 b: refs/heads/master c: be62bc410061778134c2b3b3dd93f51bb5acc839 h: refs/heads/master i: 359283: 4f5ddfa114244a1ba29153988f12f90bfa893ba9 v: v3 --- [refs] | 2 +- trunk/Documentation/DMA-API-HOWTO.txt | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index fb132aab529a..ec8ae1f4e114 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: b88a105802e9aeb6e234e8106659f5d1271081bb +refs/heads/master: be62bc410061778134c2b3b3dd93f51bb5acc839 diff --git a/trunk/Documentation/DMA-API-HOWTO.txt b/trunk/Documentation/DMA-API-HOWTO.txt index 4a4fb295ceef..65470cae471d 100644 --- a/trunk/Documentation/DMA-API-HOWTO.txt +++ b/trunk/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;