From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com, hbathini@linux.ibm.com
Subject: Re: [PATCH] powerpc/kexec_file: print error string on usable memory property update failure
Date: Wed, 1 Feb 2023 10:17:49 +0530 [thread overview]
Message-ID: <24f4aed2-9493-2bab-7cb4-385acd797adc@linux.ibm.com> (raw)
In-Reply-To: <20221216122708.182154-1-sourabhjain@linux.ibm.com>
The only place on kexec/kdump path where we don't print
reason for FDT operation failure. This patch fix that.
Will this be a good candidate for next rc?
Thanks,
Sourabh
On 16/12/22 17:57, Sourabh Jain wrote:
> Print the FDT error description along with the error message if failed
> to set the "linux,drconf-usable-memory" property in the kdump kernel's
> FDT.
>
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> ---
> arch/powerpc/kexec/file_load_64.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kexec/file_load_64.c b/arch/powerpc/kexec/file_load_64.c
> index 349a781cea0b3..7602f7e1e634e 100644
> --- a/arch/powerpc/kexec/file_load_64.c
> +++ b/arch/powerpc/kexec/file_load_64.c
> @@ -687,7 +687,8 @@ static int update_usable_mem_fdt(void *fdt, struct crash_mem *usable_mem)
> ret = fdt_setprop(fdt, node, "linux,drconf-usable-memory",
> um_info.buf, (um_info.idx * sizeof(u64)));
> if (ret) {
> - pr_err("Failed to update fdt with linux,drconf-usable-memory property");
> + pr_err("Failed to update fdt with linux,drconf-usable-memory property: %s",
> + fdt_strerror(ret));
> goto out;
> }
> }
next prev parent reply other threads:[~2023-02-01 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 12:27 [PATCH] powerpc/kexec_file: print error string on usable memory property update failure Sourabh Jain
2022-12-19 8:46 ` Hari Bathini
2022-12-21 5:38 ` Sourabh Jain
2023-02-01 4:47 ` Sourabh Jain [this message]
2023-02-20 3:49 ` Michael Ellerman
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=24f4aed2-9493-2bab-7cb4-385acd797adc@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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).