All of lore.kernel.org
 help / color / mirror / Atom feed
From: jitendra kumar khasdev <jkhasdev@gmail.com>
To: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	pankaj.saraf@nektech.in,
	jitendra kumar khasdev <jkhasdev@gmail.com>
Subject: [PATCH 2/5] Staging: comedi: fix line over 80 characters warning
Date: Sat,  3 Jan 2015 14:06:24 +0530	[thread overview]
Message-ID: <1420274187-6779-3-git-send-email-jkhasdev@gmail.com> (raw)
In-Reply-To: <1420274187-6779-1-git-send-email-jkhasdev@gmail.com>

This is patch to file pcl812.c that fix up warning line
over 80 character which is found by checkpatch tool.

Singed-off-by: Jitendra Kumar Khasdev <jkhasdev@gmail.com>
---
 drivers/staging/comedi/drivers/pcl812.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/comedi/drivers/pcl812.c b/drivers/staging/comedi/drivers/pcl812.c
index 24eb601..069af70 100644
--- a/drivers/staging/comedi/drivers/pcl812.c
+++ b/drivers/staging/comedi/drivers/pcl812.c
@@ -519,7 +519,9 @@ struct pcl812_private {
 	unsigned int hwdmaptr[2];	/*  HW PTR to DMA buf */
 	unsigned int dmabytestomove[2];	/*  how many bytes DMA transfer */
 	int next_dma_buf;	/*  which buffer is next to use */
-	unsigned int dma_runs_to_end;	/*  how many times we must switch DMA buffers */
+	unsigned int dma_runs_to_end;	/*  how many times we must switch
+					 *  DMA buffers
+					 */
 	unsigned int last_dma_run;	/*  how many bytes to transfer on last DMA buffer */
 	unsigned int max_812_ai_mode0_rangewait;	/*  setling time for gain */
 	unsigned int divisor1;
-- 
1.9.1


  parent reply	other threads:[~2015-01-03  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03  8:36 [PATCH 0/5] *** SUBJECT HERE *** jitendra kumar khasdev
2015-01-03  8:36 ` [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:20   ` Sudip Mukherjee
2015-01-03  8:36 ` jitendra kumar khasdev [this message]
2015-01-03  8:36 ` [PATCH 3/5] " jitendra kumar khasdev
2015-01-03  8:36 ` [PATCH 4/5] " jitendra kumar khasdev
2015-01-03  8:36 ` [PATCH 5/5] " jitendra kumar khasdev
2015-01-03 16:45 ` [PATCH 0/5] *** SUBJECT HERE *** Greg KH
2015-01-03 22:54   ` Paul Bolle
2015-01-04  1:41     ` Konrad Zapalowicz
2015-01-05 22:18       ` Paul Bolle
  -- strict thread matches above, loose matches on Subject: below --
2015-01-03 12:46 [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:46 ` [PATCH 2/5] " jitendra kumar khasdev

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=1420274187-6779-3-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=hsweeten@visionengravers.com \
    --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.