From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 7/7] Remove bogus comment in dma_direct_alloc_coherent()
Date: Thu, 6 Dec 2007 00:41:48 +0100 [thread overview]
Message-ID: <200712060041.49223.arnd@arndb.de> (raw)
In-Reply-To: <d35bdbd4be04065ab67b93b7a6a876a000dc4cf1.1196839256.git.michael@ellerman.id.au>
On Wednesday 05 December 2007, Michael Ellerman wrote:
> Since commit c80d9133e99de1af607314107910a2a1645efb17 (Make direct DMA use
> node local allocations) went in this comment makes no sense.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2007-12-05 23:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 7:20 [PATCH 1/7] Set archdata.dma_data for direct DMA in cell_dma_dev_setup() Michael Ellerman
2007-12-05 7:20 ` [PATCH 2/7] Add celleb_dma_dev_setup() Michael Ellerman
2007-12-05 23:40 ` Arnd Bergmann
2007-12-05 7:21 ` [PATCH 3/7] Use archdata.dma_data in dma_direct_ops Michael Ellerman
2007-12-05 23:40 ` Arnd Bergmann
2007-12-05 7:21 ` [PATCH 4/7] Have cell use its own dma_direct_offset variable Michael Ellerman
2007-12-05 23:40 ` Arnd Bergmann
2007-12-05 7:21 ` [PATCH 5/7] Have celleb " Michael Ellerman
2007-12-05 23:41 ` Arnd Bergmann
2007-12-05 7:21 ` [PATCH 6/7] Remove the global dma_direct_offset Michael Ellerman
2007-12-05 23:41 ` Arnd Bergmann
2007-12-05 7:21 ` [PATCH 7/7] Remove bogus comment in dma_direct_alloc_coherent() Michael Ellerman
2007-12-05 23:41 ` Arnd Bergmann [this message]
2007-12-05 23:38 ` [PATCH 1/7] Set archdata.dma_data for direct DMA in cell_dma_dev_setup() Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 5:42 Michael Ellerman
2008-01-21 5:42 ` [PATCH 7/7] Remove bogus comment in dma_direct_alloc_coherent() Michael Ellerman
2008-01-21 6:22 ` Benjamin Herrenschmidt
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=200712060041.49223.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).