From: jitendra kumar khasdev <jkhasdev@gmail.com>
To: gregkh@linuxfoundation.org
Cc: abbotti@mev.co.uk, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, pankaj.saraf@nektech.in,
jitendra kumar khasdev <jkhasdev@gmail.com>
Subject: [PATCH 3/3] Staging: comedi: fix space and 80 char coding style issue
Date: Mon, 29 Dec 2014 03:14:45 +0530 [thread overview]
Message-ID: <1419803085-9441-1-git-send-email-jkhasdev@gmail.com> (raw)
This is a patch to the s626.c file that fixes up spcae and maximum
character limit warning found by the checkpatch.pl tool
Signed-off-by: Jitendra Kumar Khasdev <jkhasdev@gmail.com>
---
drivers/staging/comedi/drivers/s626.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/comedi/drivers/s626.c b/drivers/staging/comedi/drivers/s626.c
index 14932c5..77f715b 100644
--- a/drivers/staging/comedi/drivers/s626.c
+++ b/drivers/staging/comedi/drivers/s626.c
@@ -118,7 +118,7 @@ static void s626_mc_enable(struct comedi_device *dev,
static void s626_mc_disable(struct comedi_device *dev,
unsigned int cmd, unsigned int reg)
{
- writel(cmd << 16 , dev->mmio + reg);
+ writel(cmd << 16, dev->mmio + reg);
mmiowb();
}
@@ -2534,7 +2534,8 @@ static int s626_initialize(struct comedi_device *dev)
for (i = 0; i < 2; i++) {
writel(S626_I2C_CLKSEL, dev->mmio + S626_P_I2CSTAT);
s626_mc_enable(dev, S626_MC2_UPLD_IIC, S626_P_MC2);
- ret = comedi_timeout(dev, NULL, NULL, s626_i2c_handshake_eoc, 0);
+ ret = comedi_timeout(dev, NULL, NULL, s626_i2c_handshake_eoc,
+ 0);
if (ret)
return ret;
}
--
1.9.1
next reply other threads:[~2014-12-28 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 21:44 jitendra kumar khasdev [this message]
2014-12-29 7:07 ` [PATCH 3/3] Staging: comedi: fix space and 80 char coding style issue Sudip Mukherjee
2014-12-29 12:11 ` Pankaj Saraf
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=1419803085-9441-1-git-send-email-jkhasdev@gmail.com \
--to=jkhasdev@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.saraf@nektech.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.