From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linux PPC <linuxppc-dev@ozlabs.org>,
Remi Machet <rmachet@slac.stanford.edu>
Subject: Re: New dma-noncoherent code, looking for comment and people to test
Date: Tue, 30 Sep 2008 17:21:30 +1000 [thread overview]
Message-ID: <1222759290.9006.47.camel@pasglop> (raw)
In-Reply-To: <77D91812-7338-462D-8361-A9A55869D515@kernel.crashing.org>
On Mon, 2008-09-29 at 13:03 -0500, Kumar Gala wrote:
>
> We really should change this code over to the new dma changes Becky's
> introduced so we just have a non-coherent set of DMA ops (thus we can
> do both non-coherent and coherent in the same system).
Yes :-)
Ben.
next prev parent reply other threads:[~2008-09-30 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 17:26 New dma-noncoherent code, looking for comment and people to test Remi Machet
2008-09-29 18:03 ` Kumar Gala
2008-09-29 18:22 ` Remi Machet
2008-09-29 18:39 ` Kumar Gala
2008-09-30 7:21 ` Benjamin Herrenschmidt [this message]
2008-09-30 7:21 ` Benjamin Herrenschmidt
2008-09-30 16:27 ` Remi Machet
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=1222759290.9006.47.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rmachet@slac.stanford.edu \
/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;
as well as URLs for NNTP newsgroup(s).