public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lijo Antony <lijo.kernel@gmail.com>
Cc: abbotti@mev.co.uk, fmhess@users.sourceforge.net,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Staging: comedi: addi_common.h: checkpatch.pl fixes
Date: Mon, 7 Jan 2013 14:39:41 -0800	[thread overview]
Message-ID: <20130107223941.GA3913@kroah.com> (raw)
In-Reply-To: <1357395175-6077-2-git-send-email-lijo.kernel@gmail.com>

On Sat, Jan 05, 2013 at 06:12:55PM +0400, Lijo Antony wrote:
> Reduced line lengths to 80 chars by removing extra spaces.
> 
> Signed-off-by: Lijo Antony <lijo.kernel@gmail.com>
> ---
>  .../staging/comedi/drivers/addi-data/addi_common.h |   20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/staging/comedi/drivers/addi-data/addi_common.h b/drivers/staging/comedi/drivers/addi-data/addi_common.h
> index 6d8b29f94..1996a68 100644
> --- a/drivers/staging/comedi/drivers/addi-data/addi_common.h
> +++ b/drivers/staging/comedi/drivers/addi-data/addi_common.h
> @@ -298,7 +298,7 @@ struct addi_private {
>  	unsigned char b_AiInitialisation;
>  	unsigned int ui_AiActualScan;	/* how many scans we finished */
>  	unsigned int ui_AiBufferPtr;	/*  data buffer ptr in samples */
> -	unsigned int ui_AiNbrofChannels;	/*  how many channels is measured */
> +	unsigned int ui_AiNbrofChannels; /*  how many channels is measured */
>  	unsigned int ui_AiScanLength;	/*  Length of actual scanlist */
>  	unsigned int ui_AiActualScanPosition;	/*  position in actual scan */
>  	unsigned int *pui_AiChannelList;	/*  actual chanlist */
> @@ -313,14 +313,14 @@ struct addi_private {
>  	short *AiData;	/*  Pointer to sample data */
>  	unsigned int ui_AiNbrofScans;	/*  number of scans to do */
>  	unsigned short us_UseDma;	/*  To use Dma or not */
> -	unsigned char b_DmaDoubleBuffer;	/*  we can use double buffering */
> +	unsigned char b_DmaDoubleBuffer; /*  we can use double buffering */
>  	unsigned int ui_DmaActualBuffer;	/*  which buffer is used now */
>  	/* UPDATE-0.7.57->0.7.68 */
>  	/* unsigned int               ul_DmaBufferVirtual[2]; pointers to begin of DMA buffer */
>  	short *ul_DmaBufferVirtual[2];	/*  pointers to begin of DMA buffer */
>  	unsigned int ul_DmaBufferHw[2];	/*  hw address of DMA buff */
> -	unsigned int ui_DmaBufferSize[2];	/*  size of dma buffer in bytes */
> -	unsigned int ui_DmaBufferUsesize[2];	/*  which size we may now used for transfer */
> +	unsigned int ui_DmaBufferSize[2]; /*  size of dma buffer in bytes */
> +	unsigned int ui_DmaBufferUsesize[2]; /* size we may use for transfer */
>  	unsigned int ui_DmaBufferSamples[2];	/*  size in samples */
>  	unsigned int ui_DmaBufferPages[2];	/*  number of pages in buffer */
>  	unsigned char b_DigitalOutputRegister;	/*  Digital Output Register */
> @@ -331,13 +331,13 @@ struct addi_private {
>  	unsigned char b_ModeSelectRegister;	/*  Contain data written at iobase + 0E */
>  	unsigned short us_OutputRegister;	/*  Contain data written at iobase + 0 */
>  	unsigned char b_InterruptState;
> -	unsigned char b_TimerInit;	/*  Specify if InitTimerWatchdog was load */
> -	unsigned char b_TimerStarted;	/*  Specify if timer 2 is running or not */
> +	unsigned char b_TimerInit; /*  Specify if InitTimerWatchdog was load */

As you didn't do this for all fields in the structure, it's not really
worth doing it for just these, right?

The proper thing to do is use kerneldoc format and document it all at
the top of the structure, care to do that instead?

thanks,

greg k-h

  reply	other threads:[~2013-01-07 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 14:12 [PATCH 1/2] Staging: comedi: addi_common.c: checkpatch.pl fixes Lijo Antony
2013-01-05 14:12 ` [PATCH 2/2] Staging: comedi: addi_common.h: " Lijo Antony
2013-01-07 22:39   ` Greg KH [this message]
2013-01-07 22:50     ` H Hartley Sweeten
2013-01-08  5:42       ` Lijo Antony

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=20130107223941.GA3913@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=lijo.kernel@gmail.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