From: ravishankarkm <ravishankarkm32@gmail.com>
To: greg@kroah.com
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
ravishankarkm <ravishankarkm32@gmail.com>
Subject: [PATCH 3/3] Staging: comedi: fix WARNING issue in s626.c
Date: Wed, 9 Mar 2016 10:59:49 +0530 [thread overview]
Message-ID: <1457501390-8844-3-git-send-email-ravishankarkm32@gmail.com> (raw)
In-Reply-To: <1457501390-8844-1-git-send-email-ravishankarkm32@gmail.com>
This is a patch to the s626.c file that fixes up a line over
80 characters issues found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
---
drivers/staging/comedi/drivers/s626.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/s626.c b/drivers/staging/comedi/drivers/s626.c
index f21c6bc..f44e11b 100644
--- a/drivers/staging/comedi/drivers/s626.c
+++ b/drivers/staging/comedi/drivers/s626.c
@@ -2543,7 +2543,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 prev parent reply other threads:[~2016-03-09 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 5:29 [PATCH 1/3] Staging: comedi: fix type " ravishankarkm
2016-03-09 5:29 ` [PATCH 2/3] Staging: comedi: fix WARNING " ravishankarkm
2016-03-09 10:34 ` Ian Abbott
2016-03-09 5:29 ` ravishankarkm [this message]
2016-03-09 10:35 ` [PATCH 3/3] " Ian Abbott
2016-03-09 10:34 ` [PATCH 1/3] Staging: comedi: fix type " Ian Abbott
2016-03-09 15:33 ` Greg KH
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=1457501390-8844-3-git-send-email-ravishankarkm32@gmail.com \
--to=ravishankarkm32@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®