From: Jingoo Han <jg1.han@samsung.com>
To: "'Mark Brown'" <broonie@kernel.org>
Cc: "'Liam Girdwood'" <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
"'Jingoo Han'" <jg1.han@samsung.com>,
"'Laxman Dewangan'" <ldewangan@nvidia.com>
Subject: [PATCH 1/3] regulator: tps80031: remove unnecessary parentheses
Date: Wed, 26 Feb 2014 10:19:30 +0900 [thread overview]
Message-ID: <002e01cf3290$ccda9430$668fbc90$%han@samsung.com> (raw)
Remove unnecessary parentheses in order to fix the following
checkpatch error.
ERROR: return is not a function, parentheses are not required
Signed-off-by: Jingoo Han <jg1.han@samsung.com>
---
drivers/regulator/tps80031-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/tps80031-regulator.c b/drivers/regulator/tps80031-regulator.c
index ac88c98..26aa6d9 100644
--- a/drivers/regulator/tps80031-regulator.c
+++ b/drivers/regulator/tps80031-regulator.c
@@ -115,7 +115,7 @@ static int tps80031_reg_is_enabled(struct regulator_dev *rdev)
ri->rinfo->state_reg, ret);
return ret;
}
- return ((reg_val & TPS80031_STATE_MASK) == TPS80031_STATE_ON);
+ return (reg_val & TPS80031_STATE_MASK) == TPS80031_STATE_ON;
}
static int tps80031_reg_enable(struct regulator_dev *rdev)
--
1.7.10.4
next reply other threads:[~2014-02-26 1:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 1:19 Jingoo Han [this message]
2014-02-26 1:21 ` [PATCH 2/3] regulator: dbx500: use seq_puts() instead of seq_printf() Jingoo Han
2014-03-19 0:19 ` Jingoo Han
2014-03-19 0:26 ` [PATCH V2] " Jingoo Han
2014-03-19 10:20 ` Mark Brown
2014-02-26 1:22 ` [PATCH 3/3] regulator: 88pm8607: fix indent code style Jingoo Han
2014-02-26 2:10 ` Haojian Zhuang
2014-02-27 4:39 ` Mark Brown
2014-03-05 4:33 ` [PATCH 1/3] regulator: tps80031: remove unnecessary parentheses Mark Brown
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='002e01cf3290$ccda9430$668fbc90$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--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).