From: ian <spyro@f2s.com>
To: Andi Kleen <ak@suse.de>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-arch@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, linux-scsi@vger.kernel.org, jejb@steeleye.com,
kernel-discuss@handhelds.org, Dmitry <dbaryshkov@gmail.com>
Subject: Re: DMA API Re: Remove dma_coherent_mem interface
Date: Wed, 20 Feb 2008 21:26:55 +0000 [thread overview]
Message-ID: <1203542815.3181.6.camel@wirenth> (raw)
In-Reply-To: <47BC7B34.7020308@suse.de>
On Wed, 2008-02-20 at 20:10 +0100, Andi Kleen wrote:
> ian wrote:
> > On Wed, 2008-02-20 at 18:49 +0100, Andi Kleen wrote:
> >>> So ... it's been 4 months. Any new users merged?
> >> At least dmam_declare_coherent_memory is completely unused as of
> >> 2.6.25-rc* I plan to remove these.
> >
> > Please do not.
>
> Do you use dma_declare_* or dmam_declare_*. The first is used
> currently. Only the second is unused.
Ah, sorry, I missed the extra 'm' as I scanned the mail.
We are using the former.
> > Dmitry and I are still working on getting the users of this into the
> > kernel.
>
> Is there a time frame on when will this happen? Will you be ready
> for the .26 merge window?
I think the big sticking point now is getting the generic clock
interface merged - Dmitry is working hard on that.
The rest of the code is pretty clean now.
> Well if it takes longer the best strategy might be to remove
> unused stuff now and you just readd what you need when you
> really need it in tree.
I think that would not be the best path now.
btw, kernel-discuss@handhelds.org appears to be a dead list these days.
next prev parent reply other threads:[~2008-02-20 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:03 DMA API Re: Remove dma_coherent_mem interface ian
2007-10-31 21:34 ` Matthew Wilcox
2007-11-01 9:48 ` ian
2007-11-01 10:07 ` Paul Mundt
2007-11-01 15:33 ` ian
2007-11-01 15:52 ` Bernhard Walle
2008-02-20 17:14 ` Matthew Wilcox
2008-02-20 17:49 ` Andi Kleen
2008-02-20 18:43 ` ian
2008-02-20 19:10 ` Andi Kleen
2008-02-20 21:26 ` ian [this message]
2008-02-20 22:55 ` Russell King
2008-02-20 23:05 ` James Bottomley
2008-02-21 16:32 ` Paul Mundt
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=1203542815.3181.6.camel@wirenth \
--to=spyro@f2s.com \
--cc=ak@suse.de \
--cc=dbaryshkov@gmail.com \
--cc=hpa@zytor.com \
--cc=jejb@steeleye.com \
--cc=kernel-discuss@handhelds.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.