qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Peter Crosthwaite" <crosthwaite.peter@gmail.com>
Subject: [Qemu-devel] [PULL 0/8] QOM CPUState patch queue 2015-10-22
Date: Thu, 22 Oct 2015 18:22:31 +0200	[thread overview]
Message-ID: <1445530959-19309-1-git-send-email-afaerber@suse.de> (raw)

Hello Peter,

This is my QOM CPU patch queue. Please pull.

Remaining maintainers should've had more than enough time to object or ack now.

Regards,
Andreas

Cc: Peter Maydell <peter.maydell@linaro.org>

Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>

The following changes since commit ca3e40e233e87f7b29442311736a82da01c0df7b:

  Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2015-10-22 12:41:44 +0100)

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 0960be7cffa7b30189f2f0f76b1ac3c8115660f3:

  disas: QOMify alpha specific disas setup (2015-10-22 15:49:40 +0200)

----------------------------------------------------------------
QOM CPUState and X86CPU

* Adoption of CPUClass::disas_set_info() hook

----------------------------------------------------------------
Peter Crosthwaite (8):
      disas: QOMify s390x specific disas setup
      disas: QOMify moxie specific disas setup
      disas: QOMify m68k specific disas setup
      disas: QOMify sparc specific disas setup
      disas: QOMify lm32 specific disas setup
      disas: QOMify sh4 specific disas setup
      disas: QOMify mips specific disas setup
      disas: QOMify alpha specific disas setup

 disas.c            | 55 ------------------------------------------------------
 target-alpha/cpu.c |  8 ++++++++
 target-lm32/cpu.c  |  7 +++++++
 target-m68k/cpu.c  |  9 ++++++++-
 target-mips/cpu.c  |  9 +++++++++
 target-moxie/cpu.c |  7 +++++++
 target-s390x/cpu.c |  8 ++++++++
 target-sh4/cpu.c   | 11 ++++++++++-
 target-sparc/cpu.c |  9 +++++++++
 9 files changed, 66 insertions(+), 57 deletions(-)

             reply	other threads:[~2015-10-22 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 16:22 Andreas Färber [this message]
2015-10-22 16:22 ` [Qemu-devel] [PULL 1/8] disas: QOMify s390x specific disas setup Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 2/8] disas: QOMify moxie " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 3/8] disas: QOMify m68k " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 4/8] disas: QOMify sparc " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 5/8] disas: QOMify lm32 " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 6/8] disas: QOMify sh4 " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 7/8] disas: QOMify mips " Andreas Färber
2015-10-22 16:22 ` [Qemu-devel] [PULL 8/8] disas: QOMify alpha " Andreas Färber
2015-10-22 17:01 ` [Qemu-devel] [PULL 0/8] QOM CPUState patch queue 2015-10-22 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=1445530959-19309-1-git-send-email-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=crosthwaite.peter@gmail.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).