From: akepner@sgi.com
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Jes Sorensen <jes@sgi.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
David Miller <davem@davemloft.net>,
Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [PATCH 0/4] allow drivers to flush in-flight DMA
Date: Thu, 27 Sep 2007 17:27:34 -0700 [thread overview]
Message-ID: <20070928002734.GL30013@sgi.com> (raw)
In-Reply-To: <20070926064950.GB30430@colo.lackof.org>
On Wed, Sep 26, 2007 at 12:49:50AM -0600, Grant Grundler wrote:
[edited out several points that I think have been already
addresed by others in this thread.]
> ....
> Defining it terms of completion queues won't mean much to most folks.
> Better to add a description of completion queues to the DMA-API.txt if
> necessary. dma_alloc_coherent() API is pretty well understood.
OK, next time I'll use a more generic description.
>
> > There are four patches in this set:
> >
> > [1/4] dma: add dma_flags_set_dmaflush() to dma interface
>
> Sorry - this feels like a "color of the shed" argument, but isn't
> this about DMA ordering attribute?
> "dmaflush" is an action and not an attribute to me.
Right - an attribute is a noun, not a verb. I'm going to try
"s/dmaflush/dmabarrier/" in the next version.
> ....
> This patch updates Documentation/DMA-mapping.txt. But it's a change to
> the generic (not PCI specific) API described in DMA-API.txt.
> Can you update that as well please?
>....
Ja, I realized that soon after hitting the send button. I'll
move the documentation to DMA-API.txt.
--
Arthur
prev parent reply other threads:[~2007-09-28 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 23:58 [PATCH 0/4] allow drivers to flush in-flight DMA akepner
2007-09-26 6:49 ` Grant Grundler
2007-09-26 15:17 ` Jesse Barnes
2007-09-26 19:29 ` Roland Dreier
2007-09-28 0:27 ` akepner [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=20070928002734.GL30013@sgi.com \
--to=akepner@sgi.com \
--cc=James.Bottomley@steeleye.com \
--cc=davem@davemloft.net \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rdreier@cisco.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