From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: peter.maydell@linaro.org, monstr@monstr.eu,
qemu-devel@nongnu.org, paul@codesourcery.com, duyl@xilinx.com,
linnj@xilinx.com, edgar.iglesias@gmail.com,
john.williams@petalogix.com
Subject: Re: [Qemu-devel] [PULL] Zynq-7000 EPP platform model
Date: Mon, 20 Feb 2012 08:24:50 +0100 [thread overview]
Message-ID: <4F41F542.3030508@suse.de> (raw)
In-Reply-To: <CAEgOgz4xLcw603BCGrORQp3WcsDu8KepE49a3g91kiheRrNkyw@mail.gmail.com>
Am 20.02.2012 07:25, schrieb Peter Crosthwaite:
> Pull Request for Zynq-7000 platform model initial support.
>
> The following changes since commit 99c7f87826337fa81f2f0f9baa9ca0a44faf90e9:
>
> input: send kbd+mouse events only to running guests. (2012-02-17
> 11:02:55 -0600)
>
> are available in the git repository at:
> git://developer.petalogix.com/private/peterc/qemu.git zynq-initial.6
Five hours between v6 and PULL are not really much for review,
especially when Europe is sleeping. There's no Acked-by or Reviewed-by
tag at all, not even Edgar's from v5.
Usually the ARM patches get picked up by Peter Maydell and then he sends
the PULL.
Me, I'm still missing a MAINTAINERS entry for hw/zynq_arm_sysctl.c and
hw/cadence_*. But that could be added as a follow-up patch.
/-F
>
> Peter A. G. Crosthwaite (4):
> cadence_uart: initial version of device model
> cadence_ttc: initial version of device model
> cadence_gem: initial version of device model
> xilinx_zynq: machine model initial version
>
> MAINTAINERS | 5 +
> Makefile.target | 4 +
> hw/cadence_gem.c | 1229 ++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/cadence_ttc.c | 439 ++++++++++++++++++
> hw/cadence_uart.c | 559 +++++++++++++++++++++++
> hw/xilinx_zynq.c | 173 +++++++
> hw/zynq_arm_sysctl.c | 532 ++++++++++++++++++++++
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-02-20 7:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 1:45 [Qemu-devel] [PATCH v6 0/4] Zynq-7000 EPP platform model Peter A. G. Crosthwaite
2012-02-20 1:37 ` Peter Crosthwaite
2012-02-20 1:45 ` [Qemu-devel] [PATCH v6 1/4] cadence_uart: initial version of device model Peter A. G. Crosthwaite
2012-02-20 18:58 ` Peter Maydell
2012-02-23 1:41 ` Peter Crosthwaite
2012-02-20 1:45 ` [Qemu-devel] [PATCH v6 2/4] cadence_ttc: " Peter A. G. Crosthwaite
2012-02-20 19:32 ` Peter Maydell
2012-02-21 13:04 ` Paul Brook
2012-02-23 1:24 ` Peter Crosthwaite
2012-02-27 15:45 ` Paul Brook
2012-02-28 1:04 ` Peter Crosthwaite
2012-02-28 1:55 ` Peter Crosthwaite
2012-02-28 12:07 ` Paul Brook
2012-02-28 13:42 ` Peter Crosthwaite
2012-02-23 1:42 ` Peter Crosthwaite
2012-02-20 1:45 ` [Qemu-devel] [PATCH v6 3/4] cadence_gem: " Peter A. G. Crosthwaite
2012-02-20 1:45 ` [Qemu-devel] [PATCH v6 4/4] xilinx_zynq: machine model initial version Peter A. G. Crosthwaite
2012-02-20 6:25 ` [Qemu-devel] [PULL] Zynq-7000 EPP platform model Peter Crosthwaite
2012-02-20 7:24 ` Andreas Färber [this message]
2012-02-24 16:37 ` Anthony Liguori
2012-02-27 4:31 ` Peter Crosthwaite
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=4F41F542.3030508@suse.de \
--to=afaerber@suse.de \
--cc=duyl@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=john.williams@petalogix.com \
--cc=linnj@xilinx.com \
--cc=monstr@monstr.eu \
--cc=paul@codesourcery.com \
--cc=peter.crosthwaite@petalogix.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).