From: Linus Walleij <linus.walleij@stericsson.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: David Vrabel <david.vrabel@csr.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Ghorai Sukumar <s-ghorai@ti.com>, Chris Ball <cjb@laptop.org>,
Adrian Hunter <adrian.hunter@nokia.com>,
Kyungmin Park <kmpark@infradead.org>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>
Subject: Re: [PATCH] mmc: agressive clocking framework v9
Date: Fri, 5 Nov 2010 09:35:17 +0100 [thread overview]
Message-ID: <4CD3C1C5.1030301@stericsson.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1011041257270.18581@xanadu.home>
Nicolas Pitre wrote:
> Maybe the runtime PM stuff is not the right abstraction for this?
Hm, yeah the bad thing is that I can't reuse the delay code
from runtime PM. But all the hazzle of creating dummy devices
nodes just to reuse runtime PM is even more disturbing.
Can I take this as your Acked-by: for the v7 patch using the old
host-local approach?
Linus Walleij
next prev parent reply other threads:[~2010-11-05 8:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 11:16 [PATCH] mmc: agressive clocking framework v9 Linus Walleij
2010-11-04 13:15 ` David Vrabel
2010-11-04 14:25 ` Linus Walleij
2010-11-04 17:01 ` Nicolas Pitre
2010-11-05 8:35 ` Linus Walleij [this message]
2010-11-05 10:03 ` Ohad Ben-Cohen
2010-11-04 21:20 ` Ohad Ben-Cohen
-- strict thread matches above, loose matches on Subject: below --
2010-11-06 5:38 Philip Rakity
2010-11-06 17:24 ` Ohad Ben-Cohen
2010-11-06 17:38 ` Philip Rakity
2010-11-07 1:44 ` Nicolas Pitre
2010-11-07 18:18 ` Philip Rakity
2010-11-08 4:33 ` Nicolas Pitre
2010-11-08 9:40 ` Linus Walleij
2010-11-08 9:45 ` Philip Rakity
2010-11-09 10:29 ` Jaehoon Chung
2010-11-09 16:52 ` Linus Walleij
2010-11-07 9:32 ` Ohad Ben-Cohen
2010-11-08 9:37 ` Linus Walleij
2010-11-08 9:47 ` Philip Rakity
2010-11-08 10:40 ` Linus Walleij
2010-11-08 18:49 ` Nicolas Pitre
2010-11-08 22:06 ` Linus Walleij
2010-11-08 18:47 ` Nicolas Pitre
2010-11-08 9:23 ` 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=4CD3C1C5.1030301@stericsson.com \
--to=linus.walleij@stericsson.com \
--cc=adrian.hunter@nokia.com \
--cc=cjb@laptop.org \
--cc=david.vrabel@csr.com \
--cc=jh80.chung@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=s-ghorai@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.