From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Documentation: fix block/biodoc.txt dma mapping description
Date: Mon, 8 Mar 2010 09:10:14 +0100 [thread overview]
Message-ID: <20100308081014.GN5768@kernel.dk> (raw)
In-Reply-To: <20100308155252Z.fujita.tomonori@lab.ntt.co.jp>
On Mon, Mar 08 2010, FUJITA Tomonori wrote:
> - It looks incorrect to use blk_rq_map_sg with pci_map_page here about
> DMA mappings. dma_map_sg?
>
> - better to use dma_map_page instead of pci_map_page.
> http://marc.info/?l=linux-kernel&m=126596737604808&w=2
Thanks, when this was written, dma_map_page() didn't exist yet.
--
Jens Axboe
prev parent reply other threads:[~2010-03-08 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 6:54 [PATCH] Documentation: fix block/biodoc.txt dma mapping description FUJITA Tomonori
2010-03-08 7:02 ` Failed to alloc 4M DMA memory in the 256M system Zhu, Yijun (NSN - CN/Beijing)
2010-03-10 10:37 ` Mark Hounschell
2010-03-08 8:10 ` Jens Axboe [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=20100308081014.GN5768@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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