From: Dave Hansen <dave@sr71.net>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
rpurdie@rpsys.net, linux-kernel@vger.kernel.org,
rgirod@confocus.com, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] LED driver for Intel NAS SS4200 series (v3)
Date: Thu, 01 Oct 2009 15:04:25 -0700 [thread overview]
Message-ID: <1254434665.29932.14.camel@nimitz> (raw)
In-Reply-To: <1254162493.28232.235.camel@Joe-Laptop.home>
On Mon, 2009-09-28 at 11:28 -0700, Joe Perches wrote:
> On Mon, 2009-09-28 at 10:51 -0700, Dave Hansen wrote:
> > On Thu, 2009-09-24 at 17:19 -0700, Andrew Morton wrote:
>
> Trivial logging comments:
>
> One of the printks is not prefaced and the printks
> and dev_printks are not consistently using either
> periods or no periods.
>
> Some possible substitutions:
>
> s/dev_printk(KERN_INFO/dev_info(/
> s/dev_printk(KERN_DEBUG/dev_dbg(/
> s/printk(KERN_INFO/pr_info(/
>
> I think it would be better to use:
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> and remove the "%s: " ... KBUILD_MODNAME
Those all sound like good suggestions and should clean things up.
> >+ printk(KERN_INFO KBUILD_MODNAME ": '%s' found\n", id->ident);
>
> Perhaps
> pr_info("Found a '%s'\n", id->ident);
>
> > + printk(KERN_DEBUG "setting blue off and amber on\n");
>
> pr_debug?
>
> > + printk(KERN_INFO "%s: skipping hardware autodetection\n",
> > + KBUILD_MODNAME);
> > + printk(KERN_INFO "\tif this works, please send the output ");
> > + printk(KERN_INFO "of 'dmidecode' to dave@sr71.net\n");
>
> I think this will look odd when printed.
> There's a tab on the second line, not on third.
> Perhaps:
> pr_info("Skipping hardware detection.\n");
> pr_info("Please send 'dmidecode' output to dave@sr71.net\n");
>
> > + printk(KERN_INFO "%s: no LED devices found\n",
> > + KBUILD_MODNAME);
> > + printk(KERN_INFO "registering %s PCI driver\n", KBUILD_MODNAME);
> > + printk(KERN_INFO "Unregistering %s driver\n", KBUILD_MODNAME);
>
> pr_info("No LED devices found\n");
> pr_info("Registering PCI driver\n");
> pr_info("Unregistering PCI driver\n");
Doing that really cleans things up nicely. Thanks for the suggestions!
-- Dave
prev parent reply other threads:[~2009-10-01 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 16:32 [PATCH] LED driver for Intel NAS SS4200 series Dave Hansen
2009-09-21 21:21 ` Richard Purdie
2009-09-25 0:19 ` Andrew Morton
2009-09-28 17:51 ` [PATCH] LED driver for Intel NAS SS4200 series (v3) Dave Hansen
2009-09-28 18:28 ` Joe Perches
2009-10-01 22:04 ` Dave Hansen [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=1254434665.29932.14.camel@nimitz \
--to=dave@sr71.net \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgirod@confocus.com \
--cc=rpurdie@rpsys.net \
/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.