From: Rusty Russell <rusty@rustcorp.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
virtualization <virtualization@lists.osdl.org>,
Andrew Morton <akpm@linux-foundation.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Define EFLAGS_IF
Date: Fri, 06 Apr 2007 12:24:08 +1000 [thread overview]
Message-ID: <1175826248.12230.668.camel@localhost.localdomain> (raw)
In-Reply-To: <46159D08.9030400@zytor.com>
On Thu, 2007-04-05 at 18:06 -0700, H. Peter Anvin wrote:
> Andi Kleen wrote:
> >
> > No processor.h is such a hodgepodge of unrelated stuff that any
> > splitting up is a good thing.
> >
>
> Fair enough. However, I'd still like to see the X86_CR* constants
> moved, too (and constants added for at least CR0 as well.)
Agreed. This was on theory of minimum damage, but since it seems to
have received a warm reception, I'd say moving the rest to
processor-flags.h would be a welcome addition.
Cheers,
Rusty.
next prev parent reply other threads:[~2007-04-06 2:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 3:16 [PATCH] Define EFLAGS_IF Rusty Russell
2007-03-22 3:24 ` Rusty Russell
2007-03-22 3:52 ` [PATCH] Use X86_EFLAGS_IF in irqflags.h, lguest Rusty Russell
2007-03-22 4:03 ` Keith Owens
2007-04-06 0:20 ` [PATCH] Define EFLAGS_IF H. Peter Anvin
2007-04-06 0:22 ` Jeremy Fitzhardinge
2007-04-06 0:29 ` H. Peter Anvin
2007-04-06 0:48 ` Andi Kleen
2007-04-06 1:06 ` H. Peter Anvin
2007-04-06 2:24 ` Rusty Russell [this message]
2007-04-06 10:30 ` Andi Kleen
2007-04-06 15:39 ` H. Peter Anvin
2007-04-09 1:11 ` Rusty Russell
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=1175826248.12230.668.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).