From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PULL 0/6] X86 patches
Date: Mon, 27 Apr 2015 20:54:24 +0200 [thread overview]
Message-ID: <20150427205400-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150427183753.GD17796@thinpad.lan.raisama.net>
On Mon, Apr 27, 2015 at 03:37:53PM -0300, Eduardo Habkost wrote:
> On Mon, Apr 27, 2015 at 08:25:20PM +0200, Andreas Färber wrote:
> > Am 27.04.2015 um 20:17 schrieb Andreas Färber:
> > > Am 27.04.2015 um 19:58 schrieb Eduardo Habkost:
> > >> The following changes since commit e1a5476354d396773e4c555f126d752d4ae58fa9:
> > >>
> > >> Open 2.4 development tree (2015-04-25 22:05:07 +0100)
> > >>
> > >> are available in the git repository at:
> > >>
> > >> git://github.com/ehabkost/qemu.git tags/x86-pull-request
> > >>
> > >> for you to fetch changes up to bdcfb55a486a5ccd04b1cf7bb1616d2a60149188:
> > >>
> > >> target-i386: Remove AMD feature flag aliases from CPU model table (2015-04-27 14:23:37 -0300)
> > >>
> > >> ----------------------------------------------------------------
> > >> X86 queue, 2015-04-27
> > >>
> > >> ----------------------------------------------------------------
> > >>
> > >> Eduardo Habkost (6):
> > >> MAINTAINERS: Add myself to X86
> > >> MAINTAINERS: Change status of X86 to Maintained
> > >> qemu-config: Accept empty option values
> > >> target-i386: Make "level" and "xlevel" properties static
> > >
> > > Small objection.
> >
> > Also, I'm missing my PC unref refactoring in your pull?
>
> I hadn't reviewed it completely (then got distracted by other tasks and
> forgot about it), sorry. I added a reminder to review it to my
> todo-list, so you can get my Reviewed-by soon.
>
> I assume Michael is OK with having it going through the x86 tree, even
> if it touches only pc.c.
I don't know which patches these are, sorry.
Was I Cc'd?
> --
> Eduardo
next prev parent reply other threads:[~2015-04-27 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:58 [Qemu-devel] [PULL 0/6] X86 patches Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 1/6] MAINTAINERS: Add myself to X86 Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 2/6] MAINTAINERS: Change status of X86 to Maintained Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 3/6] qemu-config: Accept empty option values Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 4/6] target-i386: Make "level" and "xlevel" properties static Eduardo Habkost
2015-04-27 18:23 ` Andreas Färber
2015-04-27 18:27 ` Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 5/6] target-i386: X86CPU::xlevel2 QOM property Eduardo Habkost
2015-04-27 17:58 ` [Qemu-devel] [PULL 6/6] target-i386: Remove AMD feature flag aliases from CPU model table Eduardo Habkost
2015-04-27 18:17 ` [Qemu-devel] [PULL 0/6] X86 patches Andreas Färber
2015-04-27 18:25 ` Andreas Färber
2015-04-27 18:37 ` Eduardo Habkost
2015-04-27 18:54 ` Michael S. Tsirkin [this message]
2015-04-27 19:00 ` Eduardo Habkost
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=20150427205400-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).