mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Damian Varayud <davarayud@gmail.com>
Cc: gregkh@suse.de, harmonco@engr.orst.edu,
	sam.j.richardson@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Medina Raul Ezequiel <ezemed7@gmail.com>
Subject: Re: [PATCH 3/3] Staging: comedi: fix brace coding style issue in pcl818.c
Date: Wed, 03 Nov 2010 15:32:32 -0700	[thread overview]
Message-ID: <1288823552.10236.52.camel@Joe-Laptop> (raw)
In-Reply-To: <1288819162-6330-3-git-send-email-user@netbu>

On Wed, 2010-11-03 at 18:19 -0300, Damian Varayud wrote:
> This is a patch to the pcl818.c file that fixes up braces, indentation, printk() and overlines warning
> and error at initializing variable found by the checkpatch.pl tool
>  			printk
> -			    ("comedi: A/D mode1/3 FIFO - channel dropout %d!=%d !\n",
> +			    ("comedi: A/D mode1/3 FIFO - channel "
> +			     "dropout %d!=%d !\n",

Not an improvement.
Please ignore any checkpatch long line complaints about printk formats.

Another thing you could do would be to convert these to
	printk(KERN_ERR
	       "comedi: A/D mode1/3 FIFO - channel dropout %d!=%d !\n",
	       etc);

That fixes the missing KERN_<level> and as well doesn't get any
complaint from checkpatch.

[]
> @@ -1753,22 +1800,23 @@ static int pcl818_attach(struct comedi_device *dev, struct comedi_devconfig *it)
>  
>  	/* claim our I/O space */
>  	iobase = it->options[0];
> -	printk("comedi%d: pcl818:  board=%s, ioport=0x%03lx",
> +	printk(KERN_ERR "comedi%d: pcl818:  board=%s, ioport=0x%03lx",
>  	       dev->minor, this_board->name, iobase);
>  	devpriv->io_range = this_board->io_range;
> -	if ((this_board->fifo) && (it->options[2] == -1)) {	/*  we've board with FIFO and we want to use FIFO */
> +	/*  we've board with FIFO and we want to use FIFO */
> +	if ((this_board->fifo) && (it->options[2] == -1)) {
>  		devpriv->io_range = PCLx1xFIFO_RANGE;
>  		devpriv->usefifo = 1;
>  	}
>  	if (!request_region(iobase, devpriv->io_range, "pcl818")) {
> -		printk("I/O port conflict\n");
> +		printk(KERN_ERR "I/O port conflict\n");

Not correct, these and several below are actually
continuation printks not the start of new lines.
The KERN_<level> that should be used is KERN_CONT.



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 21:19 [PATCH 1/3] Staging: comedi: fix brace coding style issue in ni_tio.c This is a patch to the ni_tio.c file that fixes up a brace, indentation and overlines warning found by the checkpatch.pl tool Signed-off-by: Varayud Damian Alfredo <davarayud@gmail.com> Damian Varayud
2010-11-03 21:19 ` [PATCH 2/3] Staging: comedi: fix brace coding style issue in pcl816.c Damian Varayud
2010-11-03 21:19 ` [PATCH 3/3] Staging: comedi: fix brace coding style issue in pcl818.c Damian Varayud
2010-11-03 22:32   ` Joe Perches [this message]
2010-11-03 21:48 ` [PATCH 1/3] Staging: comedi: fix brace coding style issue in ni_tio.c This is a patch to the ni_tio.c file that fixes up a brace, indentation and overlines warning found by the checkpatch.pl tool Signed-off-by: Varayud Damian Alfredo <davarayud@gmail.com> Joe Perches
     [not found] <[PATCH 3/3]Staging: comedi: fix brace coding style issue in pcl818.c>
2011-07-11  6:00 ` [PATCH 3/3] Staging: comedi: fix brace coding style issue in pcl818.c Ravishankar
2011-07-11  5:57   ` Joe Perches

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=1288823552.10236.52.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=davarayud@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ezemed7@gmail.com \
    --cc=gregkh@suse.de \
    --cc=harmonco@engr.orst.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam.j.richardson@gmail.com \
    /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®