From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 0/3] Make some cleanup in x86_emulate.c
Date: Mon, 24 Sep 2007 15:20:10 +0200 [thread overview]
Message-ID: <46F7B98A.7030806@qumranet.com> (raw)
In-Reply-To: <11906250562300-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Laurent Vivier wrote:
> This patch series makes some cleanups in x86_emulate.c
>
> [PATCH 1/3] move some parts of x86_decode_insn() into functions.
> [PATCH 2/3] remove _eflags and use directly ctxt->eflags
> [PATCH 3/3] remove no_wb
>
> It has been rebased to current master.
>
>
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-24 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 9:10 [PATCH 0/3] Make some cleanup in x86_emulate.c Laurent Vivier
[not found] ` <11906250562300-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-09-24 9:10 ` [PATCH 1/3] move grp decoding into functions to make x86_emulate_insn() clearer Laurent Vivier
[not found] ` <1190625056943-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-09-24 9:10 ` [PATCH 2/3] remove _eflags and use directly ctxt->eflags Laurent Vivier
[not found] ` <11906250573823-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-09-24 9:10 ` [PATCH 3/3] Remove no_wb, use dst.type = OP_NONE instead, idea stollen from xen-3.1 Laurent Vivier
2007-09-24 13:20 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-21 11:28 [PATCH 0/3] Make some cleanup in x86_emulate.c Laurent Vivier
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=46F7B98A.7030806@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=Laurent.Vivier-6ktuUTfB/bM@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 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.