From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: "Jan Beulich" <JBeulich@novell.com>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] fix x86-64 interrupt re-enabling in oops_end()
Date: Fri, 9 Sep 2005 10:45:19 +0200 [thread overview]
Message-ID: <200509091045.20104.ak@suse.de> (raw)
In-Reply-To: <43207E680200007800024547@emea1-mh.id2.novell.com>
On Thursday 08 September 2005 18:09, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Rather than blindly re-enabling interrupts in oops_end(), save their
> state
> in oope_begin() and then restore that state.
Thanks queued. Please don't do that many white space only changes
next time.
-Andi
prev parent reply other threads:[~2005-09-09 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:09 [PATCH] fix x86-64 interrupt re-enabling in oops_end() Jan Beulich
2005-09-09 8:45 ` Andi Kleen [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=200509091045.20104.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.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.