From: "Madhusudhan" <madhu.cr@ti.com>
To: "'Adrian Hunter'" <adrian.hunter@nokia.com>,
"'Linus Walleij'" <linus.walleij@stericsson.com>
Cc: "'Linus Walleij'" <linus.ml.walleij@gmail.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>,
"'Pierre Ossman'" <pierre@ossman.eu>,
<linux-arm-kernel@lists.arm.linux.org.uk>,
"'David Vrabel'" <david.vrabel@csr.com>, <marek.vasut@gmail.com>
Subject: RE: [PATCH 1/2] MMC Agressive clocking framework v5
Date: Fri, 24 Jul 2009 17:03:01 -0500 [thread overview]
Message-ID: <008801ca0caa$832f9df0$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <4A68A8D9.1020207@nokia.com>
Hi Adrian,
The patch #28 "The omap hsmmc driver code refactoring" in the series does
not seem to apply.
Regards,
Madhu
> -----Original Message-----
> From: Adrian Hunter [mailto:adrian.hunter@nokia.com]
> Sent: Thursday, July 23, 2009 1:16 PM
> To: Linus Walleij
> Cc: Linus Walleij; Andrew Morton; linux-kernel@vger.kernel.org; Pierre
> Ossman; linux-arm-kernel@lists.arm.linux.org.uk; David Vrabel;
> marek.vasut@gmail.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.
>
> Regards
> Adrian Hunter
next prev parent reply other threads:[~2009-07-24 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:26 Linus Walleij
2009-07-21 20:28 ` Linus Walleij
2009-07-21 20:35 ` Marek Vasut
2009-07-21 22:44 ` Linus Walleij
2009-07-22 0:46 ` Madhusudhan
2009-07-22 12:11 ` David Vrabel
2009-07-22 22:33 ` Linus Walleij
2009-07-23 14:15 ` David Vrabel
2009-07-23 18:15 ` Adrian Hunter
2009-07-23 20:25 ` Linus Walleij
2009-07-24 22:03 ` Madhusudhan [this message]
2009-07-24 22:59 ` Andrew Morton
2009-07-25 11:35 ` Adrian Hunter
2009-07-23 20:30 ` Linus Walleij
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='008801ca0caa$832f9df0$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@csr.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=pierre@ossman.eu \
/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
Powered by JetHome