From: peter.crosthwaite@xilinx.com
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, agraf@suse.de, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [RFC PATCH v1 0/3] Device tree cleanups
Date: Fri, 12 Jul 2013 14:27:53 +1000 [thread overview]
Message-ID: <cover.1373603020.git.peter.crosthwaite@xilinx.com> (raw)
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Fix the name stem of the devicetree API (P1 - s/qemu_devtree/qemu_fdt)
and start the error reporting cleanup (P3). Trivial patch P2 fixing an
arugment name along the way.
Looking for stylistic review comments on patch 3, before I go and apply
the change to the entire API.
Peter Crosthwaite (3):
device_tree: s/qemu_devtree/qemu_fdt globally
device_tree: qemu_fdt_setprop: Rename val_array arg
device_tree: qemu_fdt_setprop: Fixup error reporting
device_tree.c | 75 +++++++++------
hw/arm/boot.c | 25 ++---
hw/microblaze/boot.c | 4 +-
hw/ppc/e500.c | 217 ++++++++++++++++++++++---------------------
hw/ppc/e500plat.c | 6 +-
hw/ppc/mpc8544ds.c | 6 +-
hw/ppc/ppc440_bamboo.c | 28 +++---
hw/ppc/spapr_rtas.c | 16 ++--
hw/ppc/virtex_ml507.c | 2 +-
include/sysemu/device_tree.h | 133 +++++++++++++++++++++-----
10 files changed, 310 insertions(+), 202 deletions(-)
--
1.8.3.rc1.44.gb387c77.dirty
next reply other threads:[~2013-07-12 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 4:27 peter.crosthwaite [this message]
2013-07-12 4:28 ` [Qemu-devel] [RFC PATCH v1 1/3] device_tree: s/qemu_devtree/qemu_fdt globally peter.crosthwaite
2013-07-12 4:29 ` [Qemu-devel] [RFC PATCH v1 2/3] device_tree: qemu_fdt_setprop: Rename val_array arg peter.crosthwaite
2013-07-20 11:44 ` Andreas Färber
2013-07-12 4:29 ` [Qemu-devel] [RFC PATCH v1 3/3] device_tree: qemu_fdt_setprop: Fixup error reporting peter.crosthwaite
2013-07-20 2:36 ` Peter Crosthwaite
2013-07-20 12:07 ` Andreas Färber
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=cover.1373603020.git.peter.crosthwaite@xilinx.com \
--to=peter.crosthwaite@xilinx.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--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).