All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Brian Gerst <brgerst@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Pekka Enberg <penberg@kernel.org>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [RFC] x86: drop unnecessary kernel_eflags variable from 64 bit
Date: Mon, 27 Aug 2012 21:17:21 +0400	[thread overview]
Message-ID: <20120827171721.GC27096@moon> (raw)
In-Reply-To: <20120827171438.GA17289@tassilo.jf.intel.com>

On Mon, Aug 27, 2012 at 10:14:38AM -0700, Andi Kleen wrote:
> On Fri, Aug 24, 2012 at 11:58:47PM +0400, Cyrill Gorcunov wrote:
> > Hi guys,
> > 
> > I've been looking for some particular email in my mailbox when
> > found the patch below (it's dated as August 2011 ;) and think
> > it's still valid for kernel. Actually there were two patches,
> > and the second patch was unifying x86-32 with x86-64 but it
> > was doable as far as I remember.
> 
> Patch is fine for me. I did the original code, but you're right
> it's unlikely the EFLAGS will ever be extended.
> 
> Acked-by: Andi Kleen <ak@linux.intel.com>

Thanks for review, Andi!

  reply	other threads:[~2012-08-27 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 19:58 [RFC] x86: drop unnecessary kernel_eflags variable from 64 bit Cyrill Gorcunov
2012-08-24 20:02 ` Cyrill Gorcunov
2012-08-27 17:14 ` Andi Kleen
2012-08-27 17:17   ` Cyrill Gorcunov [this message]
2012-09-14  6:19 ` [tip:x86/asm] x86: Drop unnecessary kernel_eflags variable on 64-bit tip-bot for Ian Campbell

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=20120827171721.GC27096@moon \
    --to=gorcunov@openvz.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ian.campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=penberg@kernel.org \
    --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.