qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>,
	"Blue Swirl" <blauwirbel@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL] PReP patch queue 2012-08-15
Date: Thu, 10 Jan 2013 17:13:10 -0600	[thread overview]
Message-ID: <87bocwlji1.fsf@codemonkey.ws> (raw)
In-Reply-To: <50EF35FC.5010503@web.de>

Andreas Färber <andreas.faerber@web.de> writes:

> Am 15.08.2012 22:27, schrieb Andreas Färber:
>> Hello Anthony,
>> 
>> Please pull the PowerPC Reference Platform (PReP) queue into qemu.git master.
>> 
>> With Alex' and Hervé's blessing this contains both fixes for runtime errors
>> trying to use -M prep on qemu-system-ppc64 and well as some progress QOM'ifying
>> the pc87312 Super I/O chipset.
>
> Seems this pull was forgotten... I merged master, please pull for 1.4.

Please send things like this as a new top-level pull request.

Regards,

Anthony Liguori

>
> Regards,
> Andreas
>
> The following changes since commit a6308bc2224db238e72c570482717b68246a7ce0:
>
>   Merge remote-tracking branch 'kraxel/build.1' into staging (2013-01-10
> 13:26:31 -0600)
>
> are available in the git repository at:
>
>
>   git://repo.or.cz/qemu/afaerber.git prep-up
>
> for you to fetch changes up to 63e3555e80c31776285accbb4d0c14ae91c457dc:
>
>   Merge branch 'master' of git://git.qemu.org/qemu into prep-up
> (2013-01-10 21:52:28 +0100)
>
> ----------------------------------------------------------------
>
> Andreas Färber (2):
>       prep: Include devices for ppc64 as well
>       Merge branch 'master' of git://git.qemu.org/qemu into prep-up
>
> Hervé Poussineau (2):
>       prep: Add pc87312 Super I/O emulation
>       prep: Use pc87312 device instead of collection of random ISA devices
>
>  MAINTAINERS                       |    1 +
>  default-configs/ppc-softmmu.mak   |    2 +
>  default-configs/ppc64-softmmu.mak |    5 +
>  hw/Makefile.objs                  |    1 +
>  hw/pc87312.c                      |  387
> +++++++++++++++++++++++++++++++++++++
>  hw/pc87312.h                      |   66 +++++++
>  hw/ppc_prep.c                     |   39 +---
>  trace-events                      |    8 +
>  8 Dateien geändert, 477 Zeilen hinzugefügt(+), 32 Zeilen entfernt(-)
>  create mode 100644 hw/pc87312.c
>  create mode 100644 hw/pc87312.h

      reply	other threads:[~2013-01-10 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 20:27 [Qemu-devel] [PULL] PReP patch queue 2012-08-15 Andreas Färber
2012-08-15 20:27 ` [Qemu-devel] [PATCH 1/3] prep: Include devices for ppc64 as well Andreas Färber
2012-08-15 20:27 ` [Qemu-devel] [PATCH 2/3] prep: Add pc87312 Super I/O emulation Andreas Färber
2012-08-15 20:27 ` [Qemu-devel] [PATCH 3/3] prep: Use pc87312 device instead of collection of random ISA devices Andreas Färber
2012-08-15 20:30 ` [Qemu-devel] [PULL for-1.2] PReP patch queue 2012-08-15 Andreas Färber
2013-01-10 21:43 ` [Qemu-devel] [PULL] " Andreas Färber
2013-01-10 23:13   ` Anthony Liguori [this message]

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=87bocwlji1.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=andreas.faerber@web.de \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).