From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Nishka Dasgupta <nishka.dasgupta@yahoo.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: speakup: Remove return variable
Date: Tue, 19 Mar 2019 23:05:17 +0100 [thread overview]
Message-ID: <20190319220517.zgmdsz6z6objtd6c@function> (raw)
In-Reply-To: <20190319193722.9561-1-nishka.dasgupta@yahoo.com>
Nishka Dasgupta, le mer. 20 mars 2019 01:07:22 +0530, a ecrit:
> Remove return variable and return the required value directly. Issue
> suggested by Coccinelle using ret.cocci.
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: Nishka Dasgupta <nishka.dasgupta@yahoo.com>
> ---
> 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.19.1
>
--
Samuel
<s> je la connaissais pas celle la : "make: Entering an unknown directory"
-+- #ens-mim -+-
next prev parent reply other threads:[~2019-03-19 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 19:37 [PATCH] staging: speakup: Remove return variable Nishka Dasgupta
2019-03-19 20:01 ` [Outreachy kernel] " Julia Lawall
2019-03-19 22:05 ` Samuel Thibault [this message]
2019-03-20 15:55 ` NIshka Dasgupta
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=20190319220517.zgmdsz6z6objtd6c@function \
--to=samuel.thibault@ens-lyon.org \
--cc=chris@the-brannons.com \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=nishka.dasgupta@yahoo.com \
--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.