From: Andrew Morton <akpm@linux-foundation.org>
To: Matt Fleming <matt@console-pimps.org>
Cc: Chris Ball <cjb@laptop.org>,
Linus Walleij <linus.ml.walleij@gmail.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
STEricsson_nomadik_linux@list.st.com,
Hanumath Prasad <hanumath.prasad@stericsson.com>,
Kyungmin Park <kmpark@infradead.org>
Subject: Re: [PATCH] mmc: MMC 4.4 DDR support
Date: Mon, 23 Aug 2010 14:28:16 -0700 [thread overview]
Message-ID: <20100823142816.59b12253.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100823204829.GB6510@console-pimps.org>
On Mon, 23 Aug 2010 21:48:29 +0100
Matt Fleming <matt@console-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?
next prev parent reply other threads:[~2010-08-23 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 6:59 [PATCH] mmc: MMC 4.4 DDR support Hanumath Prasad
2010-07-10 5:28 ` Kyungmin Park
2010-07-10 5:29 ` Kyungmin Park
[not found] ` <81C3A93C17462B4BBD7E272753C10579169F9BD429@EXDCVYMBSTM005.EQ1STM.local>
2010-07-13 1:14 ` Kyungmin Park
2010-08-21 22:30 ` Linus Walleij
2010-08-21 22:37 ` Chris Ball
2010-08-23 7:21 ` Linus Walleij
2010-08-23 20:48 ` Matt Fleming
2010-08-23 21:28 ` Andrew Morton [this message]
2010-08-24 10:30 ` Adrian Hunter
2010-09-14 11:21 ` Chris Ball
2010-09-15 9:32 ` Ghorai, Sukumar
2010-09-20 4:34 ` Ghorai, Sukumar
2010-09-22 2:20 ` Chris Ball
2010-09-30 8:06 ` zhangfei gao
2010-09-30 22:30 ` Chris Ball
2010-09-30 22:29 ` Chris Ball
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=20100823142816.59b12253.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=cjb@laptop.org \
--cc=hanumath.prasad@stericsson.com \
--cc=kmpark@infradead.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.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