public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1a/2] x86_64: vdso32 cleanup using feature flags
Date: Fri, 11 Jul 2008 15:46:31 +0200	[thread overview]
Message-ID: <20080711134631.GA32159@elte.hu> (raw)
In-Reply-To: <4876B3C0.1070903@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Use the X86_FEATURE_SYSENTER32 to remove hard-coded CPU vendor check.
>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

nice cleanup - applied these two to tip/x86/core.

	Ingo

      reply	other threads:[~2008-07-11 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 23:22 [PATCH 1/2] x86_64: add pseudo-features for 32-bit compat syscall Jeremy Fitzhardinge
2008-07-11  1:13 ` [PATCH 1a/2] x86_64: vdso32 cleanup using feature flags Jeremy Fitzhardinge
2008-07-11 13:46   ` Ingo Molnar [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=20080711134631.GA32159@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox