From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: ian <spyro@f2s.com>, Andi Kleen <ak@suse.de>,
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 17:05:59 -0600 [thread overview]
Message-ID: <1203548760.3109.53.camel@localhost.localdomain> (raw)
In-Reply-To: <20080220225527.GA26887@flint.arm.linux.org.uk>
On Wed, 2008-02-20 at 22:55 +0000, Russell King wrote:
> On Wed, Feb 20, 2008 at 09:26:55PM +0000, ian wrote:
> >
> > On Wed, 2008-02-20 at 20:10 +0100, Andi Kleen wrote:
> > > 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.
>
> And that requires a review from my side, which I've not been able to do
> yet...
>
> It seems there's a number of dependencies that the code depends on,
> and trying to push to remove an interface which is used on to-be-merged
> code which is being _actively_ worked on to bring it to merge standard
> is just stupid - that's a recipe for forcing folk into a corner where
> they'll never have everything merged that they need for their particular
> set of code.
>
> The alternative is that the code which uses it could be merged as is,
> albiet without the dependents, so effectively it couldn't be built.
> But then it'll satisfy Andi's grep that there are users in the tree.
Don't worry. The interface fills a need (allocation of on chip or
behind bridge memory) and we have two in tree users: NCR_Q720 and
ochi-sm501, so it's not going anywhere.
James
next prev parent reply other threads:[~2008-02-20 23:06 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
2008-02-20 22:55 ` Russell King
2008-02-20 23:05 ` James Bottomley [this message]
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=1203548760.3109.53.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.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=rmk@arm.linux.org.uk \
--cc=spyro@f2s.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;
as well as URLs for NNTP newsgroup(s).