qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Laurent Vivier" <laurent@vivier.eu>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Bernhard Beschow" <shentey@gmail.com>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PULL 5/9] softmmu: Provide a clue as to why device tree loading failed
Date: Tue, 18 Jan 2022 13:28:43 +0100	[thread overview]
Message-ID: <20220118122847.636461-6-laurent@vivier.eu> (raw)
In-Reply-To: <20220118122847.636461-1-laurent@vivier.eu>

From: Bernhard Beschow <shentey@gmail.com>

fdt_open_into() obligingly returns an error code in case the operation
failed. So be obliging as well and use it in the error message.

Signed-off-by: Bernhard Beschow <shentey@gmail.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20220116114649.40859-1-shentey@gmail.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
 softmmu/device_tree.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/softmmu/device_tree.c b/softmmu/device_tree.c
index 3965c834ca62..31d106694048 100644
--- a/softmmu/device_tree.c
+++ b/softmmu/device_tree.c
@@ -60,7 +60,8 @@ void *create_device_tree(int *sizep)
     }
     ret = fdt_open_into(fdt, fdt, *sizep);
     if (ret) {
-        error_report("Unable to copy device tree in memory");
+        error_report("%s: Unable to copy device tree into memory: %s",
+                     __func__, fdt_strerror(ret));
         exit(1);
     }
 
@@ -104,7 +105,8 @@ void *load_device_tree(const char *filename_path, int *sizep)
 
     ret = fdt_open_into(fdt, fdt, dt_size);
     if (ret) {
-        error_report("Unable to copy device tree in memory");
+        error_report("%s: Unable to copy device tree into memory: %s",
+                     __func__, fdt_strerror(ret));
         goto fail;
     }
 
-- 
2.34.1



  parent reply	other threads:[~2022-01-18 13:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 12:28 [PULL 0/9] Trivial branch for 7.0 patches Laurent Vivier
2022-01-18 12:28 ` [PULL 1/9] hw/timer/etraxfs_timer: Add vmstate for ETRAX timers Laurent Vivier
2022-01-18 12:28 ` [PULL 2/9] hw/scsi/megasas: Simplify using the ldst API Laurent Vivier
2022-01-18 12:28 ` [PULL 3/9] qdev-core.h: Fix wrongly named reference to TYPE_SPLIT_IRQ Laurent Vivier
2022-01-18 12:28 ` [PULL 4/9] tests: Fix typo in check-help output Laurent Vivier
2022-01-18 12:28 ` Laurent Vivier [this message]
2022-01-18 12:28 ` [PULL 6/9] linux-user: Fix comment typo in arm cpu_loop code Laurent Vivier
2022-01-18 12:28 ` [PULL 7/9] linux-user: Rename user_force_sig tracepoint to match function name Laurent Vivier
2022-01-18 12:28 ` [PULL 8/9] linux-user: Return void from queue_signal() Laurent Vivier
2022-01-18 12:28 ` [PULL 9/9] linux-user: Remove MAX_SIGQUEUE_SIZE Laurent Vivier
2022-01-19 11:48 ` [PULL 0/9] Trivial branch for 7.0 patches Peter Maydell

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=20220118122847.636461-6-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=alistair.francis@wdc.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=shentey@gmail.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).