From: fengguang.wu@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: sunxi: fix semicolon.cocci warnings
Date: Thu, 30 Jun 2016 22:28:10 +0800 [thread overview]
Message-ID: <20160630142810.GA12218@lkp-nex05> (raw)
In-Reply-To: <201606302240.066JRFze%fengguang.wu@intel.com>
sound/soc/sunxi/sun4i-i2s.c:624:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
sun4i-i2s.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/sound/soc/sunxi/sun4i-i2s.c
+++ b/sound/soc/sunxi/sun4i-i2s.c
@@ -621,7 +621,7 @@ static int sun4i_i2s_probe(struct platfo
if (IS_ERR(i2s->regmap)) {
dev_err(&pdev->dev, "Regmap initialisation failed\n");
return PTR_ERR(i2s->regmap);
- };
+ }
i2s->mod_clk = devm_clk_get(&pdev->dev, "mod");
if (IS_ERR(i2s->mod_clk)) {
next parent reply other threads:[~2016-06-30 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201606302240.066JRFze%fengguang.wu@intel.com>
2016-06-30 14:28 ` kbuild test robot [this message]
2016-06-30 18:45 ` [PATCH] ASoC: sunxi: fix semicolon.cocci warnings Maxime Ripard
2016-07-01 9:54 ` Applied "ASoC: sunxi: fix semicolon.cocci warnings" to the asoc tree 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=20160630142810.GA12218@lkp-nex05 \
--to=fengguang.wu@intel.com \
--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).