From: drinkcat@chromium.org (Nicolas Boichat)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/3] thermal: sti: Add parentheses around bridge->ops->regmap_init call
Date: Wed, 8 Jul 2015 14:30:17 +0800 [thread overview]
Message-ID: <1436337018-32464-3-git-send-email-drinkcat@chromium.org> (raw)
In-Reply-To: <1436337018-32464-1-git-send-email-drinkcat@chromium.org>
regmap_init(...) is a macro since commit
"regmap: Use different lockdep class for each regmap init call".
That same name is used as a function pointer: prevent its expansion
by adding parentheses around the function pointer.
Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
---
drivers/thermal/st/st_thermal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/st/st_thermal.c b/drivers/thermal/st/st_thermal.c
index 76c515d..88c759d 100644
--- a/drivers/thermal/st/st_thermal.c
+++ b/drivers/thermal/st/st_thermal.c
@@ -214,7 +214,7 @@ int st_thermal_register(struct platform_device *pdev,
sensor->ops = sensor->cdata->ops;
- ret = sensor->ops->regmap_init(sensor);
+ ret = (sensor->ops->regmap_init)(sensor);
if (ret)
return ret;
--
2.4.3.573.g4eafbef
next prev parent reply other threads:[~2015-07-08 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 6:30 [PATCHv2 0/3] regmap: Use different lockdep class for each regmap init call Nicolas Boichat
2015-07-08 6:30 ` [PATCHv2 1/3] mfd: vexpress: Add parentheses around bridge->ops->regmap_init call Nicolas Boichat
2015-07-08 6:30 ` Nicolas Boichat [this message]
2015-07-08 6:30 ` [PATCHv2 3/3] regmap: Use different lockdep class for each regmap init call Nicolas Boichat
2015-07-23 8:45 ` [PATCHv2 0/3] " Nicolas Boichat
2015-07-23 16:12 ` Liviu Dudau
2015-07-24 10:32 ` 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=1436337018-32464-3-git-send-email-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.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).