All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"mchehab@redhat.com" <mchehab@redhat.com>
Subject: Re: [PATCH] Staging: dt3155v4l: Convert printk's to pr_<level>
Date: Wed, 7 Sep 2011 08:10:17 -0700	[thread overview]
Message-ID: <20110907151017.GB30361@kroah.com> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F001F39D748D0C@AUSP01VMBX24.collaborationhost.net>

On Tue, Sep 06, 2011 at 07:15:38PM -0500, H Hartley Sweeten wrote:
> On Tuesday, September 06, 2011 4:53 PM, Greg KH wrote:
> > On Thu, Sep 01, 2011 at 04:53:55PM -0700, H Hartley Sweeten wrote:
> >> Convert all the printk(KERN_<level>) messages in the driver to pr_<level>()
> >> and use pr_fmt to provide the module name.
> >
> > What's wrong with using dev_* instead of pr_*?  Lots of these should be
> > converted to that format instead, right?
> 
> Nothing... dev_* should be used when possible.
> 
> Actually all of the messages look like they are just plain noise and should
> be removed.  Especially the ones in dt3155_{init,exit}_module.  A lot of the
> ones in dt3155_probe look like noise also.
> 
> The ones in {read,write,wait}_i2c_reg just look messy.  Those functions also
> don't have a device pointer to use the dev_* functions.

Really?  It should have an i2c device somewhere.

> The ones in dt3155_irq_handler seem troublesome.  Isn't it a bad idea to output
> a kernel message in an interrupt handler?

Yes, don't do that.

> dt3155_{open,close} also look like noise.  Same with dt3155_init_board.
> 
> Maybe I should just submit a patch removing all of them?

Please do :)

thanks,

greg k-h

      reply	other threads:[~2011-09-07 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 23:53 [PATCH] Staging: dt3155v4l: Convert printk's to pr_<level> H Hartley Sweeten
2011-09-06 23:52 ` Greg KH
2011-09-07  0:15   ` H Hartley Sweeten
2011-09-07 15:10     ` 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=20110907151017.GB30361@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=hartleys@visionengravers.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@redhat.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 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.