From: Cai Huoqing <caihuoqing@baidu.com>
To: <caihuoqing@baidu.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
<linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/3] Input: colibri-vf50-ts - Make use of the helper function devm_add_action_or_reset()
Date: Wed, 22 Sep 2021 20:52:09 +0800 [thread overview]
Message-ID: <20210922125212.95-1-caihuoqing@baidu.com> (raw)
The helper function devm_add_action_or_reset() will internally
call devm_add_action(), and if devm_add_action() fails then it will
execute the action mentioned and return the error code. So
use devm_add_action_or_reset() instead of devm_add_action()
to simplify the error handling, reduce the code.
Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
---
drivers/input/touchscreen/colibri-vf50-ts.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/colibri-vf50-ts.c b/drivers/input/touchscreen/colibri-vf50-ts.c
index aa829725ded7..1a1d8e70ec40 100644
--- a/drivers/input/touchscreen/colibri-vf50-ts.c
+++ b/drivers/input/touchscreen/colibri-vf50-ts.c
@@ -271,9 +271,8 @@ static int vf50_ts_probe(struct platform_device *pdev)
if (IS_ERR(channels))
return PTR_ERR(channels);
- error = devm_add_action(dev, vf50_ts_channel_release, channels);
+ error = devm_add_action_or_reset(dev, vf50_ts_channel_release, channels);
if (error) {
- iio_channel_release_all(channels);
dev_err(dev, "Failed to register iio channel release action");
return error;
}
--
2.25.1
next reply other threads:[~2021-09-22 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:52 Cai Huoqing [this message]
2021-09-22 12:52 ` [PATCH 2/3] Input: elants_i2c - Make use of the helper function devm_add_action_or_reset() Cai Huoqing
2021-09-23 4:49 ` Dmitry Torokhov
2021-09-22 12:52 ` [PATCH 3/3] Input: raydium_i2c_ts " Cai Huoqing
2021-09-23 4:49 ` Dmitry Torokhov
2021-09-23 4:39 ` [PATCH 1/3] Input: colibri-vf50-ts " Dmitry Torokhov
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=20210922125212.95-1-caihuoqing@baidu.com \
--to=caihuoqing@baidu.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).