[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100823142816.59b12253.akpm@linux-foundation.org>
Date: Mon, 23 Aug 2010 14:28:16 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matt Fleming <matt@...sole-pimps.org>
Cc: Chris Ball <cjb@...top.org>,
Linus Walleij <linus.ml.walleij@...il.com>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
STEricsson_nomadik_linux@...t.st.com,
Hanumath Prasad <hanumath.prasad@...ricsson.com>,
Kyungmin Park <kmpark@...radead.org>
Subject: Re: [PATCH] mmc: MMC 4.4 DDR support
On Mon, 23 Aug 2010 21:48:29 +0100
Matt Fleming <matt@...sole-pimps.org> wrote:
> On Sat, Aug 21, 2010 at 06:37:45PM -0400, Chris Ball wrote:
> > Hi,
> >
> > > Hm is there some problem with this patch or has the processing of
> > > it simply stalled? When I read the thread I cannot see Hanumaths
> > > answers on the list but it looks mainly like the patch is OK and
> > > there is some chit-chat.
> > >
> > > Can it be picked up? Everyone is going to need DDR MMC for their
> > > eMMCs soon-ish.
> >
> > I'd like to dedicate more time to mmc/. Do you think it'd be useful
> > for me to catch all the patches sent to linux-mmc@ into a public Git
> > tree, and periodically report on what went upstream via akpm and
> > what's still waiting?
>
> It's possible Andrew has a reason that hasn't been picked up yet.
>
Kyungmin Park's questions didn't seem adequately answered and the
discussion kind of died.
I updated the patch and merged it, but I'd like the outstanding
question(s) resolved. ie: why do we add MMC_DDR_MODE, set it in
brq.data.flags and then never use it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists