From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: cgel.zte@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Minghao Chi <chi.minghao@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] Input: simplify the return expression of da9034_touch_probe()
Date: Thu, 12 May 2022 03:25:10 -0700 [thread overview]
Message-ID: <Ynzghmx1CkJSRVpN@google.com> (raw)
In-Reply-To: <20220429055300.3852396-1-chi.minghao@zte.com.cn>
On Fri, Apr 29, 2022 at 05:53:00AM +0000, cgel.zte@gmail.com wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> Simplify the return expression.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
> drivers/input/touchscreen/da9034-ts.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/input/touchscreen/da9034-ts.c b/drivers/input/touchscreen/da9034-ts.c
> index 2943f6a58388..dfb2604381d2 100644
> --- a/drivers/input/touchscreen/da9034-ts.c
> +++ b/drivers/input/touchscreen/da9034-ts.c
> @@ -298,7 +298,6 @@ static int da9034_touch_probe(struct platform_device *pdev)
> struct da9034_touch_pdata *pdata = dev_get_platdata(&pdev->dev);
> struct da9034_touch *touch;
> struct input_dev *input_dev;
> - int error;
>
> touch = devm_kzalloc(&pdev->dev, sizeof(struct da9034_touch),
> GFP_KERNEL);
> @@ -344,11 +343,7 @@ static int da9034_touch_probe(struct platform_device *pdev)
> touch->input_dev = input_dev;
> input_set_drvdata(input_dev, touch);
>
> - error = input_register_device(input_dev);
> - if (error)
> - return error;
> -
> - return 0;
> + return input_register_device(input_dev);
In cases where there are multiple checks/exit paths in the same function
I prefer the existing style as it requires less changes when extending.
Thanks,
--
Dmitry
prev parent reply other threads:[~2022-05-12 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 5:53 [PATCH] Input: simplify the return expression of da9034_touch_probe() cgel.zte
2022-05-12 10:25 ` Dmitry Torokhov [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=Ynzghmx1CkJSRVpN@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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