From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [Qemu-devel] [PULL for-2.0-rc1 0/1] QOM CPUState patch queue 2014-03-19
Date: Wed, 19 Mar 2014 19:52:37 +0100 [thread overview]
Message-ID: <1395255158-18414-1-git-send-email-afaerber@suse.de> (raw)
Hello Peter,
This is my current QOM CPU patch queue. Please pull.
Regards,
Andreas
Cc: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <anthony@codemonkey.ws>
Cc: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
The following changes since commit ec864874bd1c1e13c82f4096fd3957d26c70a680:
linux-user: Fix build if headers don't define _LINUX_CAPABILITY_VERSION_1 (2014-03-19 18:19:57 +0000)
are available in the git repository at:
git://github.com/afaerber/qemu-cpu.git tags/qom-cpu-for-2.0
for you to fetch changes up to c01a71c1a56fa27f43449ff59e5d03b2483658a2:
exec: Fix CPU rework fallout (2014-03-19 19:47:15 +0100)
----------------------------------------------------------------
QOM CPUState refactorings / X86CPU
* Fix pointer type mismatch
----------------------------------------------------------------
Christian Borntraeger (1):
exec: Fix CPU rework fallout
exec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2014-03-19 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 18:52 Andreas Färber [this message]
2014-03-19 18:52 ` [Qemu-devel] [PULL for-2.0 1/1] exec: Fix CPU rework fallout Andreas Färber
2014-03-19 19:35 ` [Qemu-devel] [PULL for-2.0-rc1 0/1] QOM CPUState patch queue 2014-03-19 Peter Maydell
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=1395255158-18414-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=imammedo@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).