From: David Gibson <david@gibson.dropbear.id.au>
To: aik@ozlabs.ru, mdroth@linux.vnet.ibm.com, armbru@redhat.com
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCHv3 0/9] Cleanups to error reporting on ppc and spapr
Date: Mon, 18 Jan 2016 15:24:34 +1100 [thread overview]
Message-ID: <1453091083-13931-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Another spin of my patches to clean up a bunch of error reporting in
the pseries machine type and target-ppc code, to better use the error
API.
Once reviewed, I hope to merge this into ppc-for-2.6 shortly.
Changes in v3:
* Adjusted a commit message for accuracy (suggest by Markus)
* Dropped a patch which relied on a wrong guess about the behaviour
of foreach_dynamic_sysbus_device().
Changes in v2:
* Assorted minor tweaks based on review
David Gibson (9):
ppc: Cleanup error handling in ppc_set_compat()
pseries: Cleanup error handling of spapr_cpu_init()
pseries: Clean up hash page table allocation error handling
pseries: Clean up error handling in spapr_validate_node_memory()
pseries: Cleanup error handling in spapr_vga_init()
pseries: Clean up error handling in spapr_rtas_register()
pseries: Clean up error handling in xics_system_init()
pseries: Clean up error reporting in ppc_spapr_init()
pseries: Clean up error reporting in htab migration functions
hw/ppc/spapr.c | 134 ++++++++++++++++++++++++++------------------
hw/ppc/spapr_hcall.c | 10 ++--
hw/ppc/spapr_rtas.c | 12 +---
target-ppc/cpu.h | 2 +-
target-ppc/translate_init.c | 13 +++--
5 files changed, 94 insertions(+), 77 deletions(-)
--
2.5.0
next reply other threads:[~2016-01-18 4:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 4:24 David Gibson [this message]
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 1/9] ppc: Cleanup error handling in ppc_set_compat() David Gibson
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 2/9] pseries: Cleanup error handling of spapr_cpu_init() David Gibson
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 3/9] pseries: Clean up hash page table allocation error handling David Gibson
2016-01-18 8:47 ` Thomas Huth
2016-01-18 10:21 ` Markus Armbruster
2016-01-19 1:12 ` David Gibson
2016-01-19 0:20 ` David Gibson
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 4/9] pseries: Clean up error handling in spapr_validate_node_memory() David Gibson
2016-01-18 9:15 ` Thomas Huth
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 5/9] pseries: Cleanup error handling in spapr_vga_init() David Gibson
2016-01-18 9:16 ` Thomas Huth
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 6/9] pseries: Clean up error handling in spapr_rtas_register() David Gibson
2016-01-18 9:20 ` Thomas Huth
2016-01-19 0:23 ` David Gibson
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 7/9] pseries: Clean up error handling in xics_system_init() David Gibson
2016-01-18 9:25 ` Thomas Huth
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 8/9] pseries: Clean up error reporting in ppc_spapr_init() David Gibson
2016-01-18 9:31 ` Thomas Huth
2016-01-18 10:06 ` Markus Armbruster
2016-01-19 1:23 ` David Gibson
2016-01-18 4:24 ` [Qemu-devel] [PATCHv3 9/9] pseries: Clean up error reporting in htab migration functions David Gibson
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=1453091083-13931-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).