From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: YueHaibing <yuehaibing@huawei.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] powerpc/pseries/memhotplug: Remove unused inline function dlpar_memory_remove()
Date: Fri, 14 May 2021 17:54:30 -0300 [thread overview]
Message-ID: <958eec4b-995b-e281-58d5-9f758e575b4e@gmail.com> (raw)
In-Reply-To: <20210514071041.17432-1-yuehaibing@huawei.com>
On 5/14/21 4:10 AM, YueHaibing wrote:
> dlpar_memory_remove() is never used, so can be removed.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
> arch/powerpc/platforms/pseries/hotplug-memory.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/hotplug-memory.c b/arch/powerpc/platforms/pseries/hotplug-memory.c
> index 8377f1f7c78e..3d93f1c48e23 100644
> --- a/arch/powerpc/platforms/pseries/hotplug-memory.c
> +++ b/arch/powerpc/platforms/pseries/hotplug-memory.c
> @@ -585,10 +585,6 @@ static inline int pseries_remove_mem_node(struct device_node *np)
> {
> return 0;
> }
> -static inline int dlpar_memory_remove(struct pseries_hp_errorlog *hp_elog)
> -{
> - return -EOPNOTSUPP;
> -}
> static int dlpar_remove_lmb(struct drmem_lmb *lmb)
> {
> return -EOPNOTSUPP;
>
next prev parent reply other threads:[~2021-05-14 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 7:10 [PATCH -next] powerpc/pseries/memhotplug: Remove unused inline function dlpar_memory_remove() YueHaibing
2021-05-14 20:54 ` Daniel Henrique Barboza [this message]
2021-06-06 12:08 ` 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=958eec4b-995b-e281-58d5-9f758e575b4e@gmail.com \
--to=danielhb413@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).