From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2
Date: Mon, 10 Sep 2012 17:30:06 +0200 [thread overview]
Message-ID: <20120910173006.1a2dc3da@nial.usersys.redhat.com> (raw)
In-Reply-To: <504E046F.2040305@suse.de>
On Mon, 10 Sep 2012 17:17:03 +0200
Andreas Färber <afaerber@suse.de> wrote:
> Hi Eduardo,
>
> Am 05.09.2012 22:41, schrieb Eduardo Habkost:
> > This is a small queue of patches that I consider "ready to go", that
> > didn't enter QEMU 1.2.
>
> There's so many x86 CPU series on the list again... Am I understanding
> correctly that this is the start, applying directly to master? Or does
> it have further prerequisites?
Yes, it's the start without prerequisites.
then goes "[PATCH 0/5] i386: cpu: remove duplicate feature names"
and then "[PATCH 00/22 v2] target-i386: convert CPU features into properties"
> Would be great to get one batch reviewed and applied, so that we can all
> test and review from the same base. ;)
>
> Regards,
> Andreas
>
next prev parent reply other threads:[~2012-09-10 15:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 20:41 [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 Eduardo Habkost
2012-09-05 20:41 ` [Qemu-devel] [PATCH 1/7] target-i386: Fold -cpu ?cpuid, ?model output into -cpu help, drop ?dump Eduardo Habkost
2012-09-10 9:40 ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 2/7] Drop cpu_list_id macro Eduardo Habkost
2012-09-10 9:46 ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 3/7] i386: add missing CPUID_* constants Eduardo Habkost
2012-09-10 9:57 ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 4/7] move CPU models from cpus-x86_64.conf to C Eduardo Habkost
2012-09-10 12:18 ` Igor Mammedov
2012-09-10 12:31 ` Igor Mammedov
2012-09-10 13:04 ` Igor Mammedov
2012-09-10 14:50 ` Don Slutz
2012-09-10 14:58 ` Andreas Färber
2012-09-10 15:07 ` Eduardo Habkost
2012-09-10 15:13 ` Andreas Färber
2012-09-10 15:04 ` Eduardo Habkost
2012-09-10 13:40 ` Igor Mammedov
2012-09-11 19:45 ` Don Slutz
2012-09-05 20:41 ` [Qemu-devel] [PATCH 5/7] eliminate cpus-x86_64.conf file Eduardo Habkost
2012-09-10 13:46 ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 6/7] x86_cpudef_setup: coding style change Eduardo Habkost
2012-09-11 19:45 ` Don Slutz
2012-09-05 20:41 ` [Qemu-devel] [PATCH 7/7] i386: kill cpudef config section support Eduardo Habkost
2012-09-10 14:20 ` Igor Mammedov
2012-09-10 15:17 ` [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 Andreas Färber
2012-09-10 15:30 ` Igor Mammedov [this message]
2012-09-10 15:46 ` [Qemu-devel] CPU code roadmap (was Re: [PATCH 0/7] x86 CPU patches that didn't get into 1.2) Eduardo Habkost
2012-09-11 14:59 ` Eduardo Habkost
2012-09-17 17:29 ` [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 Andreas Färber
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=20120910173006.1a2dc3da@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--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).