From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Guo Zhengkui <guozhengkui@vivo.com>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
zhengkui_guo@outlook.com
Subject: Re: [PATCH] MIPS: Sibyte: remove unnecessary return variable
Date: Thu, 12 May 2022 18:09:27 +0200 [thread overview]
Message-ID: <20220512160927.GD14475@alpha.franken.de> (raw)
In-Reply-To: <20220505030116.14371-1-guozhengkui@vivo.com>
On Thu, May 05, 2022 at 11:01:14AM +0800, Guo Zhengkui wrote:
> Fix the following coccicheck warning:
>
> arch/mips/sibyte/bcm1480/setup.c:37:5-8: Unneeded variable: "ret".
> Return "0" on line 67.
>
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
> ---
> arch/mips/sibyte/bcm1480/setup.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/mips/sibyte/bcm1480/setup.c b/arch/mips/sibyte/bcm1480/setup.c
> index 6f34b871b08e..e3e807046a9c 100644
> --- a/arch/mips/sibyte/bcm1480/setup.c
> +++ b/arch/mips/sibyte/bcm1480/setup.c
> @@ -34,8 +34,6 @@ static char *pass_str;
>
> static int __init setup_bcm1x80_bcm1x55(void)
> {
> - int ret = 0;
> -
> switch (soc_pass) {
> case K_SYS_REVISION_BCM1480_S0:
> periph_rev = 1;
> @@ -64,7 +62,7 @@ static int __init setup_bcm1x80_bcm1x55(void)
> break;
> }
>
> - return ret;
> + return 0;
> }
>
> /* Setup code likely to be common to all SiByte platforms */
> --
> 2.20.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-05-12 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 3:01 [PATCH] MIPS: Sibyte: remove unnecessary return variable Guo Zhengkui
2022-05-12 16:09 ` Thomas Bogendoerfer [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=20220512160927.GD14475@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=guozhengkui@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=zhengkui_guo@outlook.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).