All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Damian Varayud <davarayud@gmail.com>
Cc: gregkh@suse.de, arun.thomas@gmail.com, ezemed7@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: fix coding style issue in pcmuio.c
Date: Fri, 12 Nov 2010 01:24:07 +0300	[thread overview]
Message-ID: <20101111222407.GB3533@bicker> (raw)
In-Reply-To: <1289485692-1527-1-git-send-email-user@netbu>

On Thu, Nov 11, 2010 at 11:28:12AM -0300, Damian Varayud wrote:
> This is a patch to the pcmuio.c file that fixes up braces, overlines
> and printk warnings found by the checkpatch.pl tool
> 
> Signed-off-by: Ezequiel Medina <ezemed7@gmail.com>
> ---

Looks basically Ok, but there are some few problems with the comments.

>  #define REG_INT_PENDING 0x6
> -#define REG_PAGELOCK 0x7	/* page selector register, upper 2 bits select a page
> -				   and bits 0-5 are used to 'lock down' a particular
> -				   port above to make it readonly.  */
> +#define REG_PAGELOCK 0x7/* page selector register, upper 2 bits select a page
> +			   and bits 0-5 are used to 'lock down' a particular
> +			   port above to make it readonly.  */

The original spacing was better.

>  	struct {
> -		int asic;	/* if non-negative, this subdev has an interrupt asic */
> +		int asic;	/* if non-negative, this subdev has an
> +				 * interrupt asic */
>  		int first_chan;	/* if nonnegative, the first channel id for
>  				   interrupts. */

Frankly I would just leave these as is since it's barely over the 80
char mark.  But if you really want to change them then linux multi-line
commenting style is described in Documentation/CodingStyle

The preferred style for long (multi-line) comments is:

        /*
         * This is the preferred style for multi-line
         * comments in the Linux kernel source code.
         * Please use it consistently.
         *
         * Description:  A column of asterisks on the left side,
         * with beginning and ending almost-blank lines.
         */

Please redo the comments and resend.

regards,
dan carpenter



  reply	other threads:[~2010-11-11 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 14:28 [PATCH] Staging: comedi: fix coding style issue in pcmuio.c Damian Varayud
2010-11-11 22:24 ` Dan Carpenter [this message]
2010-11-16 19:43 ` 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=20101111222407.GB3533@bicker \
    --to=error27@gmail.com \
    --cc=arun.thomas@gmail.com \
    --cc=davarayud@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ezemed7@gmail.com \
    --cc=gregkh@suse.de \
    --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 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.