mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	petr@vandrovec.name,
	Glauber de Oliveira Costa <gcosta@redhat.com>
Subject: Re: Commit f06e4ec breaks vmware
Date: Mon, 04 Feb 2008 17:31:46 -0800	[thread overview]
Message-ID: <1202175106.28740.4.camel@bodhitayantram.eng.vmware.com> (raw)
In-Reply-To: <20080204153631.GA30943@elte.hu>


On Mon, 2008-02-04 at 16:36 +0100, Ingo Molnar wrote:
> * Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> 
> > On Feb 4, 2008 10:53 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > > > commit 8d947344c47a40626730bb80d136d8daac9f2060
> > > > Author: Glauber de Oliveira Costa <gcosta@redhat.com>
> > > > Date:   Wed Jan 30 13:31:12 2008 +0100
> > > >
> > > >     x86: change write_idt_entry signature
> > >
> > > does the patch below ontop of x86.git#mm fix this?
> > 
> > 
> > > 32-bit or 64-bit guest kernel?
> > 
> > 32-bit.
> > 
> > Yep, this fixed the problem.
> 
> great! I've added:
> 
>    Tested-by: Jeff Chua <jeff.chua.linux@gmail.com>
> 
> to the commit message as well, if you dont mind. Full patch is below.

Acked-by: Zachary Amsden <zach@vmware.com>

Thanks, Ingo!


  parent reply	other threads:[~2008-02-05  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 14:11 Jan Engelhardt
2008-02-04  4:19 ` Petr Vandrovec
2008-02-04 11:51 ` Ingo Molnar
2008-02-04 14:01   ` Jeff Chua
2008-02-04 14:48     ` Ingo Molnar
2008-02-04 14:53     ` Ingo Molnar
2008-02-04 15:30       ` Jeff Chua
2008-02-04 15:36         ` Ingo Molnar
2008-02-04 15:48           ` Jeff Chua
2008-02-05  1:31           ` Zachary Amsden [this message]
2008-02-04 14:58   ` Jan Engelhardt

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=1202175106.28740.4.camel@bodhitayantram.eng.vmware.com \
    --to=zach@vmware.com \
    --cc=gcosta@redhat.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=petr@vandrovec.name \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®