From: Shuah Khan <shuah.khan@hp.com>
To: Jesper Juhl <jj@chaosbits.net>, rob@landley.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
konrad.wilk@oracle.com, LKML <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah.khan@hp.com>,
linux-doc@vger.kernel.org
Subject: [PATCH] Documentation/DMA-API-HOWTO.txt - minor grammar corrections
Date: Mon, 29 Oct 2012 16:19:54 -0600 [thread overview]
Message-ID: <1351549194.2757.26.camel@lorien2> (raw)
In-Reply-To: <alpine.LNX.2.00.1210292103260.4401@swampdragon.chaosbits.net>
Minor grammar corrections.
Signed-off-by: Shuah Khan <shuah.khan@hp.com>
---
Documentation/DMA-API-HOWTO.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
index bf242bbe..14129f1 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;
--
1.7.9.5
parent reply other threads:[~2012-10-29 22:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.LNX.2.00.1210292103260.4401@swampdragon.chaosbits.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1351549194.2757.26.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=akpm@linux-foundation.org \
--cc=jj@chaosbits.net \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®