From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] x86 acpi: on wakeup, ljmp directly after writing CR0.PE
Date: Sun, 26 Oct 2008 21:38:15 +0100 [thread overview]
Message-ID: <200810262138.15669.rjw@sisk.pl> (raw)
In-Reply-To: <4904D30C.7080200@zytor.com>
On Sunday, 26 of October 2008, H. Peter Anvin wrote:
> Rafael J. Wysocki wrote:
> > Ingo, Peter,
> >
> > I have this patch in my queue, is it necessary or should I drop it?
> >
>
> It's unclear if it's necessary, but I think it's more compliant and we
> should do it.
OK, then.
Ingo, please queue. :-)
Thanks,
Rafael
prev parent reply other threads:[~2008-10-26 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 19:38 [PATCH] x86 acpi: on wakeup, ljmp directly after writing CR0.PE Rafael J. Wysocki
2008-10-26 20:29 ` H. Peter Anvin
2008-10-26 20:38 ` 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=200810262138.15669.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
/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