All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: matthieu castet <castet.matthieu@free.fr>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org
Subject: Re: [RFC] merge 32/64 bits realmode wakeup code
Date: Sat, 29 Jan 2011 16:19:01 -0800	[thread overview]
Message-ID: <4D44AE75.6020803@zytor.com> (raw)
In-Reply-To: <201101292215.57292.rjw@sisk.pl>

On 01/29/2011 01:15 PM, Rafael J. Wysocki wrote:
>
> That's correct, but those changes can wait.  The most urgent thing is to fix
> the resume regression at hand.  I guess we should ask the reporter's in
> https://bugzilla.kernel.org/show_bug.cgi?id=27472 to test that patch, right?
>

By the way, guys: I'm on vacation at the moment, but I do monitor this 
thread.  I think at this point we should revert NX for the low 1 MiB and 
worry about doing it properly for .39.  That being said, this kind of 
unification is a good thing in general.

	-hpa

  reply	other threads:[~2011-01-30  0:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 21:56 [RFC] merge 32/64 bits realmode wakeup code matthieu castet
2011-01-27 21:56 ` matthieu castet
2011-01-27 22:53 ` Rafael J. Wysocki
2011-01-29 20:43   ` matthieu castet
2011-01-29 20:43     ` matthieu castet
2011-01-29 21:15     ` Rafael J. Wysocki
2011-01-29 21:15       ` Rafael J. Wysocki
2011-01-30  0:19       ` H. Peter Anvin [this message]
2011-01-30 12:59         ` Rafael J. Wysocki
2011-01-30 19:57         ` matthieu castet
2011-01-30 19:57           ` matthieu castet
2011-01-30 20:04       ` matthieu castet
2011-01-30 20:04         ` matthieu castet
2011-01-30 22:42         ` Rafael J. Wysocki
2011-01-30 22:42           ` 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=4D44AE75.6020803@zytor.com \
    --to=hpa@zytor.com \
    --cc=castet.matthieu@free.fr \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.