From: Kevin Hilman <khilman@deeprootsystems.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: runtime PM: common hooks for static and runtime PM
Date: Thu, 25 Feb 2010 07:26:37 -0800 [thread overview]
Message-ID: <87iq9ljpzm.fsf@deeprootsystems.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1002241354560.1253-100000@iolanthe.rowland.org> (Alan Stern's message of "Wed\, 24 Feb 2010 13\:56\:33 -0500 \(EST\)")
Alan Stern <stern@rowland.harvard.edu> writes:
> On Wed, 24 Feb 2010, Mark Brown wrote:
>
>> On Mon, Feb 08, 2010 at 09:54:07AM -0500, Alan Stern wrote:
>> > On Sat, 6 Feb 2010, Alan Stern wrote:
>>
>> > > I'll give it a try and we'll see how it turns out...
>>
>> > And here it is. You can see that the patch isn't ideal.
>>
>> > Anyway, it should do what you want -- I haven't tested it.
>>
>> It's taken a little while to test (and to be frank my testing is paper
>> thin) but it looks like this does what I'm looking for - thanks!
>
> But should that patch be submitted for inclusion in the kernel,
> warts and all?
I vote yes.
Kevin
next prev parent reply other threads:[~2010-02-25 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 23:30 runtime PM: common hooks for static and runtime PM Kevin Hilman
2010-02-04 15:24 ` Alan Stern
2010-02-05 10:43 ` Mark Brown
2010-02-05 15:41 ` Alan Stern
2010-02-05 16:11 ` Mark Brown
2010-02-05 21:40 ` Alan Stern
2010-02-05 22:44 ` Mark Brown
2010-02-06 2:57 ` Alan Stern
2010-02-06 15:46 ` Mark Brown
2010-02-06 16:18 ` Alan Stern
2010-02-08 14:54 ` Alan Stern
2010-02-24 18:14 ` Mark Brown
2010-02-24 18:56 ` Alan Stern
2010-02-24 22:32 ` Mark Brown
2010-02-25 15:26 ` Kevin Hilman [this message]
2010-03-16 21:31 ` Kevin Hilman
2010-03-17 14:47 ` Alan Stern
2010-03-17 16:42 ` Kevin Hilman
2010-03-17 17:10 ` Alan Stern
2010-03-17 21:46 ` Rafael J. Wysocki
2010-03-17 22:32 ` Kevin Hilman
2010-03-18 14:13 ` Alan Stern
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=87iq9ljpzm.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/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.