From: Laurent Navet <laurent.navet@gmail.com>
To: grant.likely@secretlab.ca, linus.walleij@linaro.org
Cc: santosh.shilimkar@ti.com, khilman@ti.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
Laurent Navet <laurent.navet@gmail.com>
Subject: [PATCH 05/10] gpio: gpio-pxa.c: fix checkpatch errors
Date: Wed, 20 Mar 2013 13:15:59 +0100 [thread overview]
Message-ID: <1363781764-17330-6-git-send-email-laurent.navet@gmail.com> (raw)
In-Reply-To: <1363781764-17330-1-git-send-email-laurent.navet@gmail.com>
Fix :
gpio/gpio-pxa.c:605: ERROR: space required after that ',' (ctx:VxV)
gpio/gpio-pxa.c:672: ERROR: space prohibited after that open parenthesis '('
Signed-off-by: Laurent Navet <laurent.navet@gmail.com>
---
drivers/gpio/gpio-pxa.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-pxa.c b/drivers/gpio/gpio-pxa.c
index 9cc108d..6d01914 100644
--- a/drivers/gpio/gpio-pxa.c
+++ b/drivers/gpio/gpio-pxa.c
@@ -602,7 +602,7 @@ static int pxa_gpio_probe(struct platform_device *pdev)
for_each_gpio_chip(gpio, c) {
writel_relaxed(0, c->regbase + GFER_OFFSET);
writel_relaxed(0, c->regbase + GRER_OFFSET);
- writel_relaxed(~0,c->regbase + GEDR_OFFSET);
+ writel_relaxed(~0, c->regbase + GEDR_OFFSET);
/* unmask GPIO edge detect for AP side */
if (gpio_is_mmp_type(gpio_type))
writel_relaxed(~0, c->regbase + ED_MASK_OFFSET);
@@ -669,7 +669,7 @@ static void pxa_gpio_resume(void)
for_each_gpio_chip(gpio, c) {
/* restore level with set/clear */
- writel_relaxed( c->saved_gplr, c->regbase + GPSR_OFFSET);
+ writel_relaxed(c->saved_gplr, c->regbase + GPSR_OFFSET);
writel_relaxed(~c->saved_gplr, c->regbase + GPCR_OFFSET);
writel_relaxed(c->saved_grer, c->regbase + GRER_OFFSET);
--
1.7.10.4
next prev parent reply other threads:[~2013-03-20 12:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 12:15 GPIO - Fix " Laurent Navet
2013-03-20 12:15 ` [PATCH 01/10] gpio: gpiolib-of.c: fix checkpatch error Laurent Navet
2013-03-27 12:36 ` Linus Walleij
2013-03-20 12:15 ` [PATCH 02/10] gpio: gpio-mvebu.c: fix checkpatch errors Laurent Navet
2013-03-27 12:39 ` Linus Walleij
2013-03-20 12:15 ` [PATCH 03/10] gpio: gpio-omap.c: fix checkpatch error Laurent Navet
2013-03-20 12:24 ` Santosh Shilimkar
2013-03-20 12:33 ` Santosh Shilimkar
2013-03-27 12:41 ` Linus Walleij
2013-03-20 12:15 ` [PATCH 04/10] gpio: gpio-pca953x.c: " Laurent Navet
2013-03-27 12:42 ` Linus Walleij
2013-03-20 12:15 ` Laurent Navet [this message]
2013-03-27 12:43 ` [PATCH 05/10] gpio: gpio-pxa.c: fix checkpatch errors Linus Walleij
2013-03-20 12:16 ` [PATCH 06/10] gpio: gpio-sch.c: fix checkpatch error Laurent Navet
2013-03-27 12:44 ` Linus Walleij
2013-03-20 12:16 ` [PATCH 07/10] gpio: gpio-stp-xway.c: " Laurent Navet
2013-03-27 12:45 ` Linus Walleij
2013-03-20 12:16 ` [PATCH 08/10] gpio: gpio-tc3589x.c: fix checkpatch errors Laurent Navet
2013-03-27 12:45 ` Linus Walleij
2013-03-20 12:16 ` [PATCH 09/10] gpio: gpio-timberdale.c: fix checkpatch error Laurent Navet
2013-03-27 12:46 ` Linus Walleij
2013-03-20 12:16 ` [PATCH 10/10] gpio: gpio-tps65910.c: " Laurent Navet
2013-03-27 12:47 ` 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=1363781764-17330-6-git-send-email-laurent.navet@gmail.com \
--to=laurent.navet@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=khilman@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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
Powered by JetHome