public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: jitendra kumar khasdev <jkhasdev@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, pankaj.saraf@nektech.in
Subject: Re: [PATCH 1/5] Staging: comedi: fix line over 80 characters warning
Date: Sat, 3 Jan 2015 17:50:56 +0530	[thread overview]
Message-ID: <20150103122056.GA4765@sudip-PC> (raw)
In-Reply-To: <1420274187-6779-2-git-send-email-jkhasdev@gmail.com>

On Sat, Jan 03, 2015 at 02:06:23PM +0530, jitendra kumar khasdev wrote:
> 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>

what is Singed-off ??? why you are doing Signed-off manually? let git do it..

thanks
sudip

> ---
>  drivers/staging/comedi/drivers/pcl812.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/comedi/drivers/pcl812.c b/drivers/staging/comedi/drivers/pcl812.c
> index ac243ca..24eb601 100644
> --- a/drivers/staging/comedi/drivers/pcl812.c
> +++ b/drivers/staging/comedi/drivers/pcl812.c
> @@ -510,7 +510,8 @@ struct pcl812_private {
>  	unsigned char dma;	/*  >0 use dma ( usedDMA channel) */
>  	unsigned char range_correction;	/*  =1 we must add 1 to range number */
>  	unsigned int last_ai_chanspec;
> -	unsigned char mode_reg_int;	/*  there is stored INT number for some card */
> +	unsigned char mode_reg_int;	/*  there is stored INT number
> +					    for some card */
>  	unsigned int ai_poll_ptr;	/*  how many sampes transfer poll */
>  	unsigned int dmapages;
>  	unsigned int hwdmasize;
> -- 
> 1.9.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2015-01-03 12:21 UTC|newest]

Thread overview: 16+ 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 [this message]
2015-01-03  8:36 ` [PATCH 2/5] " jitendra kumar khasdev
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 13:25 ` Sudip Mukherjee
2015-01-04 23:41 ` Greg KH
2015-01-05  4:04   ` jitendra kumar khasdev
2015-01-05  6:00     ` 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=20150103122056.GA4765@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=jkhasdev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox