From: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: mwb@linux.vnet.ibm.com
Subject: Re: [PATCH] pseries: Fix build break for SPLPAR=n and CPU hotplug
Date: Fri, 9 Feb 2018 14:33:04 -0800 [thread overview]
Message-ID: <88d0b9a1-d995-21cb-e801-553ad64fac93@linux.vnet.ibm.com> (raw)
In-Reply-To: <151820002192.57762.14326361815004034389.stgit@ltcalpine2-lp14.aus.stglabs.ibm.com>
On 02/09/2018 10:13 AM, Nathan Fontenot wrote:
> Build break fix for SPLPAR=n builds and CPU hotplug.
>
> arch/powerpc/platforms/pseries/hotplug-cpu.o: In function `.dlpar_online_cpu':
> hotplug-cpu.c:(.text+0xc40): undefined reference to `.find_and_online_cpu_nid'
>
> Move the declaration of find_and_online_cpu_nid() to topology.h where
> we can define it as a no-op for SPLAPR=n builds.
>
> Fixes: e67e02a ("powerpc/pseries: Fix cpu hotplug crash with memoryless nodes")
> Signed-off-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> ---
Reviewed-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
prev parent reply other threads:[~2018-02-09 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 18:13 [PATCH] pseries: Fix build break for SPLPAR=n and CPU hotplug Nathan Fontenot
2018-02-09 22:33 ` Tyrel Datwyler [this message]
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=88d0b9a1-d995-21cb-e801-553ad64fac93@linux.vnet.ibm.com \
--to=tyreld@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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