From: Greg KH <greg@kroah.com>
To: Chihau Chau <chihau@gmail.com>
Cc: gregkh@suse.de, mithlesh@linsyssoft.com, reodge@gmail.com,
andrea.gelmini@gelma.net, penberg@cs.helsinki.fi,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: drivers: Code style issues
Date: Thu, 22 Jul 2010 11:47:57 -0700 [thread overview]
Message-ID: <20100722184757.GA14820@kroah.com> (raw)
In-Reply-To: <1279818473-18212-1-git-send-email-chihau@gmail.com>
On Thu, Jul 22, 2010 at 01:07:53PM -0400, Chihau Chau wrote:
> From: Chihau Chau <chihau@gmail.com>
>
> This fix some lines over 80 characters.
>
> Signed-off-by: Chihau Chau <chihau@gmail.com>
> ---
> drivers/staging/comedi/drivers.c | 17 ++++++++---------
> 1 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers.c b/drivers/staging/comedi/drivers.c
> index 4a29ed7..50c8295 100644
> --- a/drivers/staging/comedi/drivers.c
> +++ b/drivers/staging/comedi/drivers.c
> @@ -117,8 +117,8 @@ int comedi_device_attach(struct comedi_device *dev, struct comedi_devconfig *it)
>
> for (driv = comedi_drivers; driv; driv = driv->next) {
> if (!try_module_get(driv->module)) {
> - printk
> - (KERN_INFO "comedi: failed to increment module count, skipping\n");
> + printk(KERN_INFO "comedi: failed to increment module "
> + "count, skipping\n");
No, please don't break strings across lines like this, it makes it
harder to grep for things.
How about something like:
printk(KERN_INFO "comedi: failed to increment module count, skipping\n");
instead. That should pass the checkpatch.pl script, right?
thanks,
greg k-h
prev parent reply other threads:[~2010-07-22 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 17:07 [PATCH] Staging: comedi: drivers: Code style issues Chihau Chau
2010-07-22 18:47 ` Greg KH [this message]
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=20100722184757.GA14820@kroah.com \
--to=greg@kroah.com \
--cc=andrea.gelmini@gelma.net \
--cc=chihau@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.com \
--cc=penberg@cs.helsinki.fi \
--cc=reodge@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