From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Pavel Machek <pavel@ucw.cz>,
pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Lauro Salmito <laurosalmito@gmail.com>,
Magnus Damm <damm@igel.co.jp>,
Wu Fengguang <fengguang.wu@intel.com>,
Sergio Luis <sergio@larces.uece.br>
Subject: Re: [GIT PULL] PM updates for 2.6.31
Date: Sat, 13 Jun 2009 00:44:09 +0200 [thread overview]
Message-ID: <200906130044.11273.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.01.0906121317320.3237@localhost.localdomain>
On Friday 12 June 2009, Linus Torvalds wrote:
>
> On Fri, 12 Jun 2009, Rafael J. Wysocki wrote:
>
> > Hi Linus,
> >
> > Please pull power management updates for 2.6.31 from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git for-linus
> >
> > They are cleanups and code rearrangements mostly, in particular:
> >
> > * arch/x86/power/cpu_(32|64) unification from Sergio Luis (Ingo saw
> > these patches and his opinion was that they should better go
> > through the suspend tree)
> >
> > * Removal of some unused files and PM callbacks, function renames
> > from Magnus Damm and Alan Stern
> >
> > * Rearrangements of the code under kernel/power from me and
> > Cornelia Huck
> >
> > * Two patches related to the memory shrinking (for the record, Pavel
> > doesn't like the "PM/Suspend: Do not shrink memory before suspend"
> > patch, so please let me know if I should drop it)
> >
> > * A couple of bug fixes
> >
> >
> > arch/x86/power/cpu.c | 259 +++++++++++
> > arch/x86/power/cpu_32.c | 148 ------
> > arch/x86/power/cpu_64.c | 174 -------
> > kernel/power/disk.c | 955 --------------------------------------
> > kernel/power/hibernate.c | 955 ++++++++++++++++++++++++++++++++++++++
> > kernel/power/hibernate_nvs.c | 135 ++++++
> > 35 files changed, 2056 insertions(+), 2194 deletions(-)
>
> Please add rename detection to your pull script (and --summary, for that
> matter). This _should_ have looked like
>
> 33 files changed, 984 insertions(+), 1122 deletions(-)
>
> because it would have detected this:
>
> rename arch/x86/power/{cpu_64.c => cpu.c} (62%)
> delete mode 100644 arch/x86/power/cpu_32.c
> rename kernel/power/{disk.c => hibernate.c} (96%)
>
> instead of counting those as some huge patches that add/remove code.
I will, sorry for not doing it this time and thanks for pulling.
Best,
Rafael
prev parent reply other threads:[~2009-06-12 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 20:02 [GIT PULL] PM updates for 2.6.31 Rafael J. Wysocki
2009-06-12 20:06 ` Pavel Machek
2009-06-12 20:19 ` Linus Torvalds
2009-06-12 22:44 ` 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=200906130044.11273.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cornelia.huck@de.ibm.com \
--cc=damm@igel.co.jp \
--cc=fengguang.wu@intel.com \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jaswinder@kernel.org \
--cc=laurosalmito@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=sergio@larces.uece.br \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
/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