public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Move CONFIG_X86 decleration to be x86 specific in configure	script
Date: Fri, 30 Nov 2007 10:14:48 +0200	[thread overview]
Message-ID: <474FC678.7000107@qumranet.com> (raw)
In-Reply-To: <6fa44248cb3ad7b8a75e.1196356446@thinkpad>

Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> # Date 1196356414 21600
> # Node ID 6fa44248cb3ad7b8a75ea7c23ee935103547fee4
> # Parent  eb2a8d4d818eb0b27feec303e028bd9944a28694
> Move CONFIG_X86 decleration to be x86 specific in configure script
>
> In the configure script CONFIG_X86 is explicitly declared for
> qemu. Now while today the support for other archs is not exactly
> in kvm just yet (it's coming)..this shouldn't be specified for
> everyone ;-)
>
>   

Applied, thanks.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

  reply	other threads:[~2007-11-30  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 17:14 [PATCH] Move CONFIG_X86 decleration to be x86 specific in configure script Jerone Young
2007-11-30  8:14 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-05 21:50 Jerone Young

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=474FC678.7000107@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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