From: Andrew Donnellan <ajd@linux.ibm.com>
To: cgel.zte@gmail.com, fbarrat@linux.ibm.com
Cc: ye xingchen <ye.xingchen@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>,
linux-kernel@vger.kernel.org, npiggin@gmail.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH linux-next] ocxl: Remove the unneeded result variable
Date: Wed, 07 Sep 2022 17:34:43 +1000 [thread overview]
Message-ID: <744e04b545ed8f9a87c9728041169bb9b55edfad.camel@linux.ibm.com> (raw)
In-Reply-To: <20220906072006.337099-1-ye.xingchen@zte.com.cn>
On Tue, 2022-09-06 at 07:20 +0000, cgel.zte@gmail.com wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
>
> Return the value opal_npu_spa_clear_cache() directly instead of
> storing
> it in another redundant variable.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
> ---
> arch/powerpc/platforms/powernv/ocxl.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/platforms/powernv/ocxl.c
> b/arch/powerpc/platforms/powernv/ocxl.c
> index 27c936075031..629067781cec 100644
> --- a/arch/powerpc/platforms/powernv/ocxl.c
> +++ b/arch/powerpc/platforms/powernv/ocxl.c
> @@ -478,10 +478,8 @@ EXPORT_SYMBOL_GPL(pnv_ocxl_spa_release);
> int pnv_ocxl_spa_remove_pe_from_cache(void *platform_data, int
> pe_handle)
> {
> struct spa_data *data = (struct spa_data *) platform_data;
> - int rc;
>
> - rc = opal_npu_spa_clear_cache(data->phb_opal_id, data->bdfn,
> pe_handle);
> - return rc;
> + return opal_npu_spa_clear_cache(data->phb_opal_id, data-
> >bdfn, pe_handle);
> }
> EXPORT_SYMBOL_GPL(pnv_ocxl_spa_remove_pe_from_cache);
>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2022-09-07 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 7:20 [PATCH linux-next] ocxl: Remove the unneeded result variable cgel.zte
2022-09-07 7:34 ` Andrew Donnellan [this message]
2022-10-04 13:26 ` 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=744e04b545ed8f9a87c9728041169bb9b55edfad.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=cgel.zte@gmail.com \
--cc=fbarrat@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=ye.xingchen@zte.com.cn \
--cc=zealci@zte.com.cn \
/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).