From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC 0/7] Runtime PM updates for autosuspend
Date: Fri, 24 Sep 2010 22:06:18 +0200 [thread overview]
Message-ID: <201009242206.18131.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1009241122380.1744-100000@iolanthe.rowland.org>
On Friday, September 24, 2010, Alan Stern wrote:
> On Fri, 24 Sep 2010, Rafael J. Wysocki wrote:
>
> > On Thursday, September 23, 2010, Alan Stern wrote:
> > > Rafael and Greg:
> >
> > Hi,
> >
> > > The following series of emails contains my proposed patches for the
> > > runtime PM core, leading up to a general "autosuspend" implementation.
> > > This is going to be one of those difficult cross-subsystem things,
> > > because the first patch in the series affects sysfs whereas the rest
> > > affect PM. (In addition, there are two other patches I'm not going to
> > > include here that update USB to take advantage of the new PM
> > > facilities. Ultimately there will be changes to the SCSI, block, and
> > > IDE layers as well -- they're not written yet.)
> > >
> > > We can decide on the best plan for merging these later on. For now I
> > > would simply like to post them for review and comments. These are not
> > > yet necessarily in final form, but I think they are pretty close. They
> > > apply on top of 2.6.36-rc5.
> > >
> > > Alan Stern
> > >
> > >
> > > 1/7: Add sysfs_merge_group() and sysfs_unmerge_group() routines
> > > for later use by PM and USB.
> > >
> > > 2/7: Move the runtime PM accounting routines away from the functions
> > > that do the actual work.
> > >
> > > 3/7: Replace runtime PM boolean arguments with bitflags.
> > >
> > > 4/7: Merge the synchronous and asynchronous runtime PM routines.
> > >
> > > 5/7: Regroup the public entry points for runtime PM into three
> > > simple functions.
> > >
> > > 6/7: Add the "no_callbacks" flag.
> > >
> > > 7/7: Implement autosuspend.
> >
> > The series generally looks good to me, except for a few comments, mostly
> > related to the names of various things I sent in my replies to the specific
> > patches.
>
> Your points were all well taken. I'll revise the patches and submit
> them. Do you think it's too late for them to appear in the next merge
> window?
No, it's not. I actually would like to push them for .37.
Thanks,
Rafael
next prev parent reply other threads:[~2010-09-24 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 21:22 [RFC 0/7] Runtime PM updates for autosuspend Alan Stern
2010-09-23 22:44 ` Rafael J. Wysocki
2010-09-24 15:25 ` Alan Stern
2010-09-24 20:06 ` Rafael J. Wysocki [this message]
2010-09-24 20:38 ` 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=201009242206.18131.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox