From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PM core: rename suspend and resume functions
Date: Sun, 24 May 2009 23:06:30 +0200 [thread overview]
Message-ID: <200905242306.30415.rjw@sisk.pl> (raw)
In-Reply-To: <aec7e5c30905210054q24c121dfj555e9029beb39686@mail.gmail.com>
On Thursday 21 May 2009, Magnus Damm wrote:
> On Tue, May 19, 2009 at 11:53 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> > This patch (as1241) renames a bunch of functions in the PM core.
> > Rather than go through a boring list of name changes, suffice it to
> > say that in the end we have a bunch of pairs of functions:
> >
> > device_resume_noirq dpm_resume_noirq
> > device_resume dpm_resume
> > device_complete dpm_complete
> > device_suspend_noirq dpm_suspend_noirq
> > device_suspend dpm_suspend
> > device_prepare dpm_prepare
> >
> > in which device_X does the X operation on a single device and dpm_X
> > invokes device_X for all devices in the dpm_list.
> >
> > In addition, the old dpm_power_up and device_resume_noirq have been
> > combined into a single function (dpm_resume_noirq).
> >
> > Lastly, dpm_suspend_start and dpm_resume_end are the renamed versions
> > of the former top-level device_suspend and device_resume routines.
> >
> > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
>
> Looks like a bigger step in the right direction. =)
> Applied on top of next-20090520, compiles fine on SuperH with
> sh7724_generic_defconfig.
>
> Acked-by: Magnus Damm <damm@igel.co.jp>
Patch applied to the suspend-2.6 tree (linux-next branch).
Thanks,
Rafael
prev parent reply other threads:[~2009-05-24 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 14:53 [PATCH] PM core: rename suspend and resume functions Alan Stern
2009-05-21 7:54 ` Magnus Damm
2009-05-24 21:06 ` Rafael J. Wysocki [this message]
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=200905242306.30415.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=magnus.damm@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox