From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>, patches@linaro.org
Subject: [Qemu-devel] [PATCH 0/7] ARM boards: don't prematurely explode QEMUMachineInitArgs
Date: Tue, 23 Oct 2012 18:04:23 +0100 [thread overview]
Message-ID: <1351011870-1680-1-git-send-email-peter.maydell@linaro.org> (raw)
A lot of the ARM board models follow the pattern of having a
single common init function which is called with various
parameters from the QEMUMachine init function for several board
model variants. The change to QEMUMachineInitArgs in commit 5f072e
took the fairly mechanical approach of splitting the QEMUMachineInitArgs
fields out in each variant's init function to pass to an unchanged
common init function. This is a bit repetitive, so clean them up
to just pass the QEMUMachineInitArgs directly to the common
function instead.
Peter Maydell (7):
hw/vexpress.c: Don't prematurely explode QEMUMachineInitArgs
hw/realview.c: Don't prematurely explode QEMUMachineInitArgs
hw/versatilepb: Don't prematurely explode QEMUMachineInitArgs
hw/spitz: Don't prematurely explode QEMUMachineInitArgs
hw/omap_sx1: Don't prematurely explode QEMUMachineInitArgs
hw/nseries: Don't prematurely explode QEMUMachineInitArgs
hw/mainstone: Don't prematurely explode QEMUMachineInitArgs
hw/mainstone.c | 21 ++++++-----------
hw/nseries.c | 39 +++++++++----------------------
hw/omap_sx1.c | 36 ++++++++---------------------
hw/realview.c | 68 +++++++++++++++---------------------------------------
hw/spitz.c | 45 ++++++++----------------------------
hw/versatilepb.c | 44 +++++++++--------------------------
hw/vexpress.c | 38 ++++++++----------------------
7 files changed, 76 insertions(+), 215 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-10-23 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 17:04 Peter Maydell [this message]
2012-10-23 17:04 ` [Qemu-devel] [PATCH 1/7] hw/vexpress.c: Don't prematurely explode QEMUMachineInitArgs Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 2/7] hw/realview.c: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 3/7] hw/versatilepb: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 4/7] hw/spitz: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 5/7] hw/omap_sx1: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 6/7] hw/nseries: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 7/7] hw/mainstone: " Peter Maydell
2012-10-24 8:42 ` [Qemu-devel] [PATCH 0/7] ARM boards: don't " Markus Armbruster
2012-10-24 9:21 ` Peter Maydell
2012-10-24 12:06 ` Markus Armbruster
2012-10-24 12:10 ` Eduardo Habkost
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=1351011870-1680-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=ehabkost@redhat.com \
--cc=patches@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).