From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>,
linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/kexec_file: print error string on usable memory property update failure
Date: Wed, 21 Dec 2022 11:08:53 +0530 [thread overview]
Message-ID: <c821613d-bb7c-31ae-821e-95b0e86df452@linux.ibm.com> (raw)
In-Reply-To: <7118ca5c-f83a-007f-20f0-2fd65c1ef5a7@linux.ibm.com>
On 19/12/22 14:16, Hari Bathini wrote:
>
>
> On 16/12/22 5:57 pm, 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>
>
> LGTM
>
> Acked-by: Hari Bathini <hbathini@linux.ibm.com>
Thanks!
- Sourabh Jain
next prev parent reply other threads:[~2022-12-21 5:40 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 [this message]
2023-02-01 4:47 ` Sourabh Jain
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=c821613d-bb7c-31ae-821e-95b0e86df452@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).