public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: linux-pm@lists.linux-foundation.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [linux-pm] Q: x86 suspend/hibernation code consolidation
Date: Fri, 25 Jan 2008 21:47:26 -0500	[thread overview]
Message-ID: <200801252147.27254.lenb@kernel.org> (raw)
In-Reply-To: <200801260132.09529.rjw@sisk.pl>

On Friday 25 January 2008 19:32, Rafael J. Wysocki wrote:
> Hi,
> 
> 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.
> 
> When is the right time for making changes like that?
> 
> Rafael

In Cambridge, when we discussed cleanups that touch a lot of files
but have no functional change -- somebody suggested that right
after rc1 closes is a good time.  The reasoning was that they
would not conflict with the functional changes in rc1.

However, I recall Linus saying something about "Andrew is special"
WRT permission to push cleanups after the rc1 window; so I don't
know what the final ruling was -- if there was such a ruling.

-Len

  reply	other threads:[~2008-01-26  2:48 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 ` Len Brown [this message]
2008-01-26 23:42   ` [linux-pm] " 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

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=200801252147.27254.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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