From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Pavel Machek <pavel@ucw.cz>,
pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>
Subject: Re: Q: x86 suspend/hibernation code consolidation
Date: Mon, 28 Jan 2008 16:01:40 +0100 [thread overview]
Message-ID: <200801281601.41651.rjw@sisk.pl> (raw)
In-Reply-To: <20080128140350.GB27928@elte.hu>
On Monday, 28 of January 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > I'd like to move the 64-bit suspend/hibernation files from
> > arch/x86/kernel to arch/x86/power, modify the names of the 32-bit
> > files already in arch/x86/power and update the Makefiles accordingly,
> > but there are some changes queued for merging that touch the files in
> > question.
>
> nice cleanup.
>
> > When is the right time for making changes like that?
>
> best would be after the x86.git merge. We could push this via x86.git in
> fact, to line it up with whatever other changes there might be. -mm
> would be fine too, if there are pending patches in this area in -mm.
There is one patch in acpi.git, AFAICS, so I guess I'd have to wait for both
x86.git and acpi.git with that, which means -rc1 time frame more or less.
> (and i recall you did some global-scope suspend/resume changes that
> might interfere?)
Some of them are in acpi.git and some have been merged already.
Thanks,
Rafael
prev parent reply other threads:[~2008-01-28 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 0:32 Q: x86 suspend/hibernation code consolidation Rafael J. Wysocki
2008-01-26 2:47 ` [linux-pm] " Len Brown
2008-01-26 23:42 ` Rafael J. Wysocki
2008-01-26 9:42 ` Pavel Machek
2008-01-26 23:36 ` Rafael J. Wysocki
2008-01-28 14:03 ` Ingo Molnar
2008-01-28 15:01 ` 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=200801281601.41651.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
/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