From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: jallen@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/pseries: Fix build break when MEMORY_HOTREMOVE=n
Date: Wed, 15 Feb 2017 21:41:54 -0600 [thread overview]
Message-ID: <aa351118-d400-be1e-5b48-136eefc9ca7d@linux.vnet.ibm.com> (raw)
In-Reply-To: <1487214078-3893-1-git-send-email-mpe@ellerman.id.au>
On 02/15/2017 09:01 PM, Michael Ellerman wrote:
> We broke the build when CONFIG_MEMORY_HOTREMOVE=n:
>
> arch/powerpc/platforms/pseries/hotplug-memory.c:821:8: error: implicit
> declaration of function 'dlpar_memory_readd_by_index'
>
> Add a dummy to fix it.
>
> Fixes: e70d59700fc3 ("powerpc/pseries: Introduce memory hotplug READD operation")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Looks like we both saw the same thing today, this was patch 1/4 in the
'Implement indexed-count memory hotplug' patchset I sent out earlier today.
Perhaps I should have sent that as a separate patch.
Reviewed-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> ---
> arch/powerpc/platforms/pseries/hotplug-memory.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/platforms/pseries/hotplug-memory.c b/arch/powerpc/platforms/pseries/hotplug-memory.c
> index 3381c20edbc0..b3b92814ce87 100644
> --- a/arch/powerpc/platforms/pseries/hotplug-memory.c
> +++ b/arch/powerpc/platforms/pseries/hotplug-memory.c
> @@ -628,7 +628,10 @@ static int dlpar_memory_remove_by_index(u32 drc_index, struct property *prop)
> {
> return -EOPNOTSUPP;
> }
> -
> +static int dlpar_memory_readd_by_index(u32 drc_index, struct property *prop)
> +{
> + return -EOPNOTSUPP;
> +}
> #endif /* CONFIG_MEMORY_HOTREMOVE */
>
> static int dlpar_add_lmb(struct of_drconf_cell *lmb)
>
next prev parent reply other threads:[~2017-02-16 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 3:01 [PATCH] powerpc/pseries: Fix build break when MEMORY_HOTREMOVE=n Michael Ellerman
2017-02-16 3:41 ` Nathan Fontenot [this message]
2017-02-16 4:21 ` Michael Ellerman
2017-02-16 5:59 ` 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=aa351118-d400-be1e-5b48-136eefc9ca7d@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.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