From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Laurent Dufour <ldufour@linux.ibm.com>,
linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: eric.devolder@oracle.com, kexec@lists.infradead.org,
bhe@redhat.com, hbathini@linux.ibm.com
Subject: Re: [PATCH v5 1/5] powerpc/kexec: make update_cpus_node non-static
Date: Wed, 22 Jun 2022 14:10:32 +0530 [thread overview]
Message-ID: <bc8f37cb-006a-0c33-2de8-1481b4201be1@linux.ibm.com> (raw)
In-Reply-To: <2df3da07-9384-d8b2-15f5-b124538b93c2@linux.ibm.com>
On 21/06/22 14:29, Laurent Dufour wrote:
> On 20/06/2022, 09:01:02, Sourabh Jain wrote:
>> Make the update_cpus_node function non-static and export it for
>> usage in other kexec components.
>>
>> The update_cpus_node definition is moved to core_64.c so that it
>> can be used with both kexec_load and kexec_file_load system calls.
>>
>> No functional change intended.
> And FWIW
> Reviewed-by: Laurent Dufour <laurent.dufour@fr.ibm.com>
Thank you!
- Sourabh Jain
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-06-22 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 7:01 [PATCH v5 0/5] In kernel handling of CPU hotplug events for crash kernel Sourabh Jain
2022-06-20 7:01 ` [PATCH v5 1/5] powerpc/kexec: make update_cpus_node non-static Sourabh Jain
2022-06-21 8:59 ` Laurent Dufour
2022-06-22 8:40 ` Sourabh Jain [this message]
2022-06-20 7:01 ` [PATCH v5 2/5] powerpc/crash hp: update kimage_arch struct Sourabh Jain
2022-06-20 7:01 ` [PATCH v5 3/5] powerpc/crash hp: add crash hotplug support for kexec_file_load Sourabh Jain
2022-06-22 15:11 ` Laurent Dufour
2022-06-20 7:01 ` [PATCH v5 4/5] powerpc/crash hp: add crash hotplug support for kexec_load Sourabh Jain
2022-06-22 15:25 ` Laurent Dufour
2022-06-20 7:01 ` [PATCH v5 5/5] powerpc/crash hp: add crash page helper functions Sourabh Jain
2022-06-22 15:33 ` Laurent Dufour
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=bc8f37cb-006a-0c33-2de8-1481b4201be1@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=ldufour@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--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).