From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/2] Generic per-device coherent dma allocator
Date: Tue, 1 Jul 2008 19:15:08 -0700 [thread overview]
Message-ID: <200807011915.08540.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080630105835.GA27466@elte.hu>
On Monday, June 30, 2008 3:58 am Ingo Molnar wrote:
> * Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
> > Currently x86_32, sh and cris-v32 provide per-device coherent dma
> > memory allocator. However their implementation is nearly identical.
> > Refactor out common code to be reused by them.
>
> looks good to me in principle.
>
> Andrew, Jesse: i've put this aside into the core/generic-dma-coherent
> git tree which you can check at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> core/generic-dma-coherent
>
> there's some interaction with other x86 bits so i guess it would be best
> to carry this in -tip.
>
> Do the generic bits look good to you? (find the shortlog and diff below)
> It's not yet propagated into linux-next, pending your ack/nak and
> pending some test exposure.
Yeah, looks great to me; if you have dependent changes you can push it; I
don't think I have anything in my tree that'll cause real trouble.
Jesse
next prev parent reply other threads:[~2008-07-02 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 10:18 Dmitry Baryshkov
2008-06-30 10:58 ` Ingo Molnar
2008-07-02 2:15 ` Jesse Barnes [this message]
2008-07-08 21:18 ` Dmitry
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=200807011915.08540.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®