From: Joerg Roedel <joerg.roedel@amd.com>
To: Shuah Khan <shuah.khan@hp.com>
Cc: <mtk.manpages@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
<konrad.wilk@oracle.com>, <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
<devel@linuxdriverproject.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <shuahkhan@gmail.com>
Subject: Re: [PATCH v2] Documentation DMA-API-HOWTO.txt Add dma mapping error check usage examples
Date: Wed, 24 Oct 2012 17:09:11 +0200 [thread overview]
Message-ID: <20121024150911.GC2764@amd.com> (raw)
In-Reply-To: <1350590458.2680.44.camel@lorien2>
On Thu, Oct 18, 2012 at 02:00:58PM -0600, Shuah Khan wrote:
> Enhance the document to discuss the importance of dma mapping error checks
> after dma_map_single() and dma_map_page() calls. Also added usage examples
> that include unmap examples in error paths when dma mapping error is returned.
> Includes correct and incorrect usages to high light some common mistakes in
> error paths especially when dma mapping fails when more than one dma mapping
> call is made.
>
> Signed-off-by: Shuah Khan <shuah.khan@hp.com>
Applied, thanks.
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2012-10-24 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:54 [PATCH] Documentation DMA-API-HOWTO.txt Add dma mapping error check usage examples Shuah Khan
2012-10-18 9:47 ` Dan Carpenter
2012-10-18 10:13 ` Michael Kerrisk (man-pages)
2012-10-18 14:30 ` Shuah Khan
2012-10-18 20:00 ` [PATCH v2] " Shuah Khan
2012-10-18 21:32 ` Jesper Juhl
2012-10-19 16:57 ` Konrad Rzeszutek Wilk
2012-10-24 15:09 ` Joerg Roedel [this message]
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=20121024150911.GC2764@amd.com \
--to=joerg.roedel@amd.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rob@landley.net \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.com \
/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