From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: randy.dunlap@oracle.com
Cc: fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, muli@il.ibm.com, alexisb@us.ibm.com
Subject: Re: [PATCH 1/2] add the device argument to dma_mapping_error
Date: Thu, 15 May 2008 10:12:25 +0900 [thread overview]
Message-ID: <20080515101207T.tomof@acm.org> (raw)
In-Reply-To: <20080513083901.2f571418.randy.dunlap@oracle.com>
On Tue, 13 May 2008 08:39:01 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Tue, 13 May 2008 15:04:51 +0900 FUJITA Tomonori wrote:
>
> > dma_mapping_error doesn't take a pointer to the device unlike other
> > DMA operations. So we can't have dma_mapping_ops per device.
> >
> > Note that POWER already has dma_mapping_ops per device but all the
> > POWER IOMMUs use the same dma_mapping_error function. x86 IOMMUs use
> > different dma_mapping_error functions. So dma_mapping_error needs the
> > device argument.
> >
> > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
(snip)
> Seems to be missing updates to Documentation/DMA-API.txt ??
Oops, I'll post an updated version against -mm soon.
Thanks,
next prev parent reply other threads:[~2008-05-15 1:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 6:04 [PATCH 0/2] x86: per-device dma_mapping_ops FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 1/2] add the device argument to dma_mapping_error FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 2/2] x86: per-device dma_mapping_ops support FUJITA Tomonori
2008-05-14 5:55 ` Muli Ben-Yehuda
2008-05-15 20:45 ` Yinghai Lu
2008-05-16 3:44 ` FUJITA Tomonori
2008-05-13 15:39 ` [PATCH 1/2] add the device argument to dma_mapping_error Randy Dunlap
2008-05-15 1:12 ` FUJITA Tomonori [this message]
2008-05-14 5:49 ` [PATCH 0/2] x86: per-device dma_mapping_ops Muli Ben-Yehuda
2008-05-15 1:12 ` FUJITA Tomonori
2008-05-15 2:00 ` Alexis Bruemmer
2008-05-15 2:30 ` FUJITA Tomonori
2008-05-15 18:21 ` Alexis Bruemmer
2008-05-15 15:17 ` Muli Ben-Yehuda
2008-05-15 15:15 ` Muli Ben-Yehuda
2008-05-15 9:01 ` Andi Kleen
2008-05-15 9:16 ` FUJITA Tomonori
2008-05-15 9:30 ` Andi Kleen
2008-05-15 9:41 ` FUJITA Tomonori
2008-05-15 10:48 ` Andi Kleen
2008-05-15 15:32 ` Muli Ben-Yehuda
2008-05-16 3:44 ` FUJITA Tomonori
2008-05-16 5:24 ` Andi Kleen
2008-05-19 6:32 ` FUJITA Tomonori
2008-05-15 15:26 ` Muli Ben-Yehuda
2008-05-15 21:03 ` Andi Kleen
2008-05-15 21:39 ` Muli Ben-Yehuda
2008-05-15 21:45 ` Andi Kleen
2008-05-15 21:53 ` Muli Ben-Yehuda
2008-05-15 22:05 ` Muli Ben-Yehuda
2008-05-15 18:25 ` Alexis Bruemmer
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=20080515101207T.tomof@acm.org \
--to=fujita.tomonori@lab.ntt.co.jp \
--cc=akpm@linux-foundation.org \
--cc=alexisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=randy.dunlap@oracle.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