mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Maurice Dawson <mauricedawson2699@gmail.com>
Cc: gregkh@suse.de, wfp5p@virginia.edu, stewart_r@aliencamel.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: fix over 80 character coding style issues in ni_labpc.c
Date: Thu, 17 Jun 2010 13:36:22 -0700	[thread overview]
Message-ID: <20100617203622.GB32523@kroah.com> (raw)
In-Reply-To: <1275123944-1886-1-git-send-email-mauricedawson2699@gmail.com>

On Sat, May 29, 2010 at 10:05:44AM +0100, Maurice Dawson wrote:
> This is a patch to the ni_labpc.c file that fixes most over 80 character warnings found by the checkpatch.pl tool. Two lines, 4 and 1035 have not been changed because readability is better and no information is hidden
> 
> Signed-off-by: Maurice Dawson <mauricedawson2699@gmail.com>
> ---
>  drivers/staging/comedi/drivers/ni_labpc.c |   81 ++++++++++++++++++++---------
>  1 files changed, 57 insertions(+), 24 deletions(-)
> 
> diff --git a/drivers/staging/comedi/drivers/ni_labpc.c b/drivers/staging/comedi/drivers/ni_labpc.c
> index 67c8a53..bf063ad 100644
> --- a/drivers/staging/comedi/drivers/ni_labpc.c
> +++ b/drivers/staging/comedi/drivers/ni_labpc.c
> @@ -738,7 +738,8 @@ static int labpc_attach(struct comedi_device *dev, struct comedi_devconfig *it)
>  		break;
>  	case pcmcia_bustype:
>  		printk
> -		    (" this driver does not support pcmcia cards, use ni_labpc_cs.o\n");
> +		    ("this driver does not support pcmcia cards, "
> +							"use ni_labpc_cs.o\n");

Ick, no, don't break these types of strings.  Newer versions of
checkpatch will not complain about this.

>  	if (mode == MODE_SINGLE_CHAN_INTERVAL) {
>  		if (cmd->chanlist_len > 0xff) {
> -			comedi_error(dev,
> -				     "ni_labpc: chanlist too long for single channel interval mode\n");
> +			comedi_error(dev, "ni_labpc: chanlist too long "
> +							"for single channel "
> +							"interval mode\n");

Same here, don't do this.

>  			return 1;
>  		}
>  	}
> @@ -881,23 +883,29 @@ static int labpc_ai_chanlist_invalid(const struct comedi_device *dev,
>  		switch (mode) {
>  		case MODE_SINGLE_CHAN_INTERVAL:
>  			if (CR_CHAN(cmd->chanlist[i]) != channel) {
> -				comedi_error(dev,
> -					     "channel scanning order specified in chanlist is not supported by hardware.\n");
> +				comedi_error(dev, "channel scanning order "
> +							"specified in chanlist "
> +							"is not supported "
> +							"by hardware.\n");

Nor here.

>  				return 1;
>  			}
>  			break;
>  		case MODE_MULT_CHAN_UP:
>  			if (CR_CHAN(cmd->chanlist[i]) != i) {
> -				comedi_error(dev,
> -					     "channel scanning order specified in chanlist is not supported by hardware.\n");
> +				comedi_error(dev, "channel scanning order "
> +							"specified in chanlist "
> +							"is not supported "
> +							"by hardware.\n");

Or here.

>  				return 1;
>  			}
>  			break;
>  		case MODE_MULT_CHAN_DOWN:
>  			if (CR_CHAN(cmd->chanlist[i]) !=
>  			    cmd->chanlist_len - i - 1) {
> -				comedi_error(dev,
> -					     "channel scanning order specified in chanlist is not supported by hardware.\n");
> +				comedi_error(dev, "channel scanning order "
> +							"specified in chanlist "
> +							"is not supported "
> +							"by hardware.\n");

Or here, or the rest of the printk() lines.

Care to resend this without those types of changes?

thanks,

greg k-h

  reply	other threads:[~2010-06-17 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  9:05 Maurice Dawson
2010-06-17 20:36 ` Greg KH [this message]
2010-06-17 21:14   ` 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=20100617203622.GB32523@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mauricedawson2699@gmail.com \
    --cc=stewart_r@aliencamel.com \
    --cc=wfp5p@virginia.edu \
    /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®