From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [Qemu-devel] [PULL 0/6] QOM CPUState patch queue 2015-03-10
Date: Tue, 10 Mar 2015 19:22:14 +0100 [thread overview]
Message-ID: <1426011740-17688-1-git-send-email-afaerber@suse.de> (raw)
Hello Peter,
This is my QOM CPU patch queue. Please pull.
Regards,
Andreas
Cc: Peter Maydell <peter.maydell@linaro.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>
The following changes since commit 1976058109890892db8ec88bfd3273f79c459f6b:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2015-03-10 14:01:22 +0000)
are available in the git repository at:
git://github.com/afaerber/qemu-cpu.git tags/qom-cpu-for-peter
for you to fetch changes up to 2994fd96d986578a342f2342501b4ad30f6d0a85:
cpu: Make cpu_init() return QOM CPUState object (2015-03-10 17:33:51 +0100)
----------------------------------------------------------------
QOM CPUState and X86CPU
* Add CPUClass documentation
* Clean up X86CPU APIC realization
* Cleanups around cpu_init()
----------------------------------------------------------------
Eduardo Habkost (4):
target-unicore32: Make uc32_cpu_init() return UniCore32CPU
m68k: Use cpu_m68k_init()
unicore32: Use uc32_cpu_init()
cpu: Make cpu_init() return QOM CPUState object
Markus Armbruster (1):
target-i386: Clean up misuse of qdev_init() in realize method
Peter Maydell (1):
cpu: Add missing documentation for some CPUClass methods
bsd-user/main.c | 6 +++---
hw/m68k/dummy_m68k.c | 6 ++++--
hw/unicore32/puv3.c | 6 ++++--
include/qom/cpu.h | 12 ++++++++++++
linux-user/main.c | 10 +++++-----
target-alpha/cpu.h | 9 +--------
target-arm/cpu.h | 9 +--------
target-cris/cpu.h | 9 +--------
target-i386/cpu.c | 8 ++------
target-i386/cpu.h | 9 +--------
target-lm32/cpu.h | 9 +--------
target-m68k/cpu.h | 9 +--------
target-microblaze/cpu.h | 9 +--------
target-mips/cpu.h | 9 +--------
target-moxie/cpu.h | 9 +--------
target-openrisc/cpu.h | 9 +--------
target-ppc/cpu.h | 9 +--------
target-s390x/cpu.h | 2 +-
target-sh4/cpu.h | 9 +--------
target-sparc/cpu.h | 9 +--------
target-tricore/cpu.h | 10 +---------
target-unicore32/cpu.h | 6 ++++--
target-unicore32/helper.c | 10 ++--------
target-xtensa/cpu.h | 9 +--------
24 files changed, 52 insertions(+), 150 deletions(-)
next reply other threads:[~2015-03-10 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 18:22 Andreas Färber [this message]
2015-03-10 18:22 ` [Qemu-devel] [PULL 1/6] cpu: Add missing documentation for some CPUClass methods Andreas Färber
2015-03-10 18:22 ` [Qemu-devel] [PULL 2/6] target-i386: Clean up misuse of qdev_init() in realize method Andreas Färber
2015-03-10 18:22 ` [Qemu-devel] [PULL 3/6] target-unicore32: Make uc32_cpu_init() return UniCore32CPU Andreas Färber
2015-03-10 18:22 ` [Qemu-devel] [PULL 4/6] m68k: Use cpu_m68k_init() Andreas Färber
2015-03-10 18:22 ` [Qemu-devel] [PULL 5/6] unicore32: Use uc32_cpu_init() Andreas Färber
2015-03-10 18:22 ` [Qemu-devel] [PULL 6/6] cpu: Make cpu_init() return QOM CPUState object Andreas Färber
2015-03-11 14:26 ` [Qemu-devel] [PULL 0/6] QOM CPUState patch queue 2015-03-10 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=1426011740-17688-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--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).