From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Himadri Pandya <himadri18.07@gmail.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2] staging: speakup: remove unnecessary assignment statement before return
Date: Sat, 9 Mar 2019 10:11:33 +0100 [thread overview]
Message-ID: <20190309091133.uyhjrmiipm2rahnu@function> (raw)
In-Reply-To: <20190309090927.26925-1-himadri18.07@gmail.com>
Himadri Pandya, le sam. 09 mars 2019 14:39:27 +0530, a ecrit:
> Remove unnecessary assignment statement before return from function
> find_specifier_end. Issue found by Coccinelle.
Well, I have to say that for style I prefer the way it was: we apply
several functions to the input variable, before returning it.
> Signed-off-by: Himadri Pandya <himadri18.07@gmail.com>
> ---
> Changes in V2:
> - Remove "Coccinelle" from patch tag
>
> drivers/staging/speakup/i18n.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/speakup/i18n.c b/drivers/staging/speakup/i18n.c
> index ee240d36f947..a748eb8052d1 100644
> --- a/drivers/staging/speakup/i18n.c
> +++ b/drivers/staging/speakup/i18n.c
> @@ -470,8 +470,7 @@ static char *find_specifier_end(char *input)
> input++; /* Advance over %. */
> input = skip_flags(input);
> input = skip_width(input);
> - input = skip_conversion(input);
> - return input;
> + return skip_conversion(input);
> }
>
> /*
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-03-09 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 8:07 [PATCH Coccinelle] staging: speakup: remove unnecessary assignment statement before return Himadri Pandya
2019-03-09 8:13 ` [Outreachy kernel] " Julia Lawall
2019-03-09 9:09 ` [PATCH v2] " Himadri Pandya
2019-03-09 9:11 ` Samuel Thibault [this message]
2019-03-09 10:37 ` [Outreachy kernel] " Himadri Pandya
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=20190309091133.uyhjrmiipm2rahnu@function \
--to=samuel.thibault@ens-lyon.org \
--cc=chris@the-brannons.com \
--cc=gregkh@linuxfoundation.org \
--cc=himadri18.07@gmail.com \
--cc=kirk@reisers.ca \
--cc=outreachy-kernel@googlegroups.com \
--cc=w.d.hubbs@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.