[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090724155935.22f854f9.akpm@linux-foundation.org>
Date: Fri, 24 Jul 2009 15:59:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Madhusudhan" <madhu.cr@...com>
Cc: adrian.hunter@...ia.com, linus.walleij@...ricsson.com,
linus.ml.walleij@...il.com, linux-kernel@...r.kernel.org,
pierre@...man.eu, linux-arm-kernel@...ts.arm.linux.org.uk,
david.vrabel@....com, marek.vasut@...il.com
Subject: Re: [PATCH 1/2] MMC Agressive clocking framework v5
On Fri, 24 Jul 2009 17:03:01 -0500
"Madhusudhan" <madhu.cr@...com> wrote:
>
> > -----Original Message-----
> > From: Adrian Hunter [mailto:adrian.hunter@...ia.com]
> > Sent: Thursday, July 23, 2009 1:16 PM
> > To: Linus Walleij
> > Cc: Linus Walleij; Andrew Morton; linux-kernel@...r.kernel.org; Pierre
> > Ossman; linux-arm-kernel@...ts.arm.linux.org.uk; David Vrabel;
> > marek.vasut@...il.com; Madhusudhan Chikkature
> > Subject: Re: [PATCH 1/2] MMC Agressive clocking framework v5
> >
> > Hi
> >
> > Have you considered using our enable/disable approach instead?
> >
> > It is here:
> >
> > http://groups.google.com/group/linux.kernel/browse_frm/thread/a5caec1de127
> > 4be5/2ba7dee2a187a268
> >
> > Perhaps it meets your needs, whereas your patches do not seem
> > to cover the functionality we need.
> >
>
> The patch #28 "The omap hsmmc driver code refactoring" in the series does
> not seem to apply.
(top-posting repaired - please don't!)
I got one reject when applying that patch, due to
mmc-register-mmci-omap-hs-using-platform_driver_probe.patch. It was
simple to fix that up.
--
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