From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] target-i386: Small code cleanup
Date: Wed, 04 Mar 2015 15:05:28 +0100 [thread overview]
Message-ID: <54F71128.6080908@suse.de> (raw)
In-Reply-To: <20150304122838.GC13041@thinpad.lan.raisama.net>
Am 04.03.2015 um 13:28 schrieb Eduardo Habkost:
> On Tue, Feb 03, 2015 at 04:08:56PM -0200, Eduardo Habkost wrote:
>> Just two small code cleanups in target-i386/cpu.c.
>>
>> Patch 1/2 changes behavior of "-cpu ?" to not print feature names in reverse
>> order anymore. Patch 2/2 doesn't introduce any behavior changes.
>
> Andreas, just to confirm: is this series in your queue?
No, this is perfectly within target-i386 scope, so please keep it in
your queue for resubmission.
Thanks,
Andreas
>> Eduardo Habkost (2):
>> target-i386: Simplify listflags() function
>> target-i386: Eliminate unnecessary get_cpuid_vendor() function
>>
>> target-i386/cpu.c | 62 ++++++++++++++++++-------------------------------------
>> 1 file changed, 20 insertions(+), 42 deletions(-)
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2015-03-04 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 18:08 [Qemu-devel] [PATCH 0/2] target-i386: Small code cleanup Eduardo Habkost
2015-02-03 18:08 ` [Qemu-devel] [PATCH 1/2] target-i386: Simplify listflags() function Eduardo Habkost
2015-02-06 16:02 ` Paolo Bonzini
2015-02-03 18:08 ` [Qemu-devel] [PATCH 2/2] target-i386: Eliminate unnecessary get_cpuid_vendor() function Eduardo Habkost
2015-02-03 18:18 ` Andreas Färber
2015-03-04 12:28 ` [Qemu-devel] [PATCH 0/2] target-i386: Small code cleanup Eduardo Habkost
2015-03-04 14:05 ` Andreas Färber [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=54F71128.6080908@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).