Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Patrice Chotard <patrice.chotard@st.com>
Cc: kbuild-all@01.org, linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre TORGUE <alexandre.torgue@st.com>
Subject: [PATCH] gpio: stmpe: fix semicolon.cocci warnings
Date: Wed, 17 Jan 2018 10:34:05 +0800	[thread overview]
Message-ID: <20180117023405.GA124815@lkp-hsx03> (raw)
In-Reply-To: <201801171059.dszJh8JT%fengguang.wu@intel.com>

From: Fengguang Wu <fengguang.wu@intel.com>

drivers/gpio/gpio-stmpe.c:201:2-3: Unneeded semicolon


 Remove unneeded semicolon.

Generated by: scripts/coccinelle/misc/semicolon.cocci

Fixes: bb628176dbc5 ("gpio: stmpe: i2c transfer are forbiden in atomic context")
CC: Patrice Chotard <patrice.chotard@st.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 gpio-stmpe.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/gpio/gpio-stmpe.c
+++ b/drivers/gpio/gpio-stmpe.c
@@ -198,7 +198,7 @@ static void stmpe_gpio_irq_sync_unlock(s
 	if (stmpe->partnum == STMPE1600) {
 		stmpe_reg_read(stmpe, stmpe->regs[STMPE_IDX_GPMR_LSB]);
 		stmpe_reg_read(stmpe, stmpe->regs[STMPE_IDX_GPMR_CSB]);
-	};
+	}
 
 	for (i = 0; i < CACHE_NR_REGS; i++) {
 		/* STMPE801 and STMPE1600 don't have RE and FE registers */

  reply	other threads:[~2018-01-17  2:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17  2:34 [gpio:devel 68/75] drivers/gpio/gpio-stmpe.c:201:2-3: Unneeded semicolon kbuild test robot
2018-01-17  2:34 ` kbuild test robot [this message]
2018-01-17  8:26   ` [PATCH] gpio: stmpe: fix semicolon.cocci warnings Patrice CHOTARD
2018-01-17  9:21   ` Linus Walleij

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=20180117023405.GA124815@lkp-hsx03 \
    --to=fengguang.wu@intel.com \
    --cc=alexandre.torgue@st.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=patrice.chotard@st.com \
    /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