From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org,
Daniel Henrique Barboza <danielhb413@gmail.com>
Subject: [PATCH v3 0/4] enhance error handling in kvmppc_read_int*
Date: Thu, 7 Jul 2022 18:30:11 -0300 [thread overview]
Message-ID: <20220707213015.552104-1-danielhb413@gmail.com> (raw)
Hi,
In this v3 I changed the error report after fopen() to use
error_setg_errno(), as suggested by Cedric.
I also cut patch 1/1 because it's simpler to do all the function changes
in a single patch instead of having a separated patch just to change the
return value of both.
Changes from v2:
- former patch 1/1: dropped
- patch 1 (former 3):
- use error_setg_errno() instead of error_setg()
- v2 link: https://lists.gnu.org/archive/html/qemu-devel/2022-07/msg01167.html
Daniel Henrique Barboza (3):
target/ppc: enhance error report in kvmppc_read_int_cpu_dt()
target/ppc: use g_autofree in kvmppc_read_int_cpu_dt()
target/ppc: exit(1) on failure in kvmppc_get_clockfreq()
jianchunfu (1):
target/ppc: add error report when fopen fails in kvmppc_read_int_dt()
target/ppc/kvm.c | 46 +++++++++++++++++++++++++++++++---------------
1 file changed, 31 insertions(+), 15 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-07 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 21:30 Daniel Henrique Barboza [this message]
2022-07-07 21:30 ` [PATCH v3 1/4] target/ppc: add error report when fopen fails in kvmppc_read_int_dt() Daniel Henrique Barboza
2022-07-07 21:30 ` [PATCH v3 2/4] target/ppc: enhance error report in kvmppc_read_int_cpu_dt() Daniel Henrique Barboza
2022-07-07 21:30 ` [PATCH v3 3/4] target/ppc: use g_autofree " Daniel Henrique Barboza
2022-07-07 21:30 ` [PATCH v3 4/4] target/ppc: exit(1) on failure in kvmppc_get_clockfreq() Daniel Henrique Barboza
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=20220707213015.552104-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--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).