linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Joe Perches <joe@perches.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>
Subject: Re: [PATCH 0/6] drivers/ide Convert printk(KERN_<foo> to pr_<foo>(
Date: Mon, 18 May 2009 21:15:28 +0000	[thread overview]
Message-ID: <1242681328.6347.38.camel@localhost.localdomain> (raw)
In-Reply-To: <1242680389.1572.127.camel@Joe-Laptop.home>

On Mon, 2009-05-18 at 13:59 -0700, Joe Perches wrote:
> On Mon, 2009-05-18 at 15:56 +0000, James Bottomley wrote:
> > What exactly is the point of a mechanical conversion from
> > printk(KERN_ ...) to pr_...?
> > 
> > I can see the value of the pr_ macros from new code in that the
> > temptation to put a comma after KERN_.. for some people is irresistible
> > so it's an interface that's very easy to misuse, but given that we have
> > correct uses, why convert them?
> 
> Enables easier conversion to dev_<foo> macros

Don't buy this ... this should just be done directly to avoid code
churn.

> Allows easier prefixing via pr_fmt

Buy this, but you need to say what you're proposing for pr_fmt in IDE
for this to make sense.

> Puts back together unnecessarily chopped up format strings

Staying out of this bikeshed colour discussion.

> Standardization is good

We'd only be standardising if printk is deprecated, which I don't think
it is.

> Just for the hell of it

Don't like this ... it's not good for the stability of the code base and
it can cause problems with subsidiary committers by generating
unnecessary patch rejections due to code churn.

James



  reply	other threads:[~2009-05-18 21:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1242609803.git.joe@perches.com>
2009-05-18  2:21 ` [PATCH 1/6] drivers/ide: Convert printk(KERN_DEBUG to pr_debug( Joe Perches
2009-05-18  9:34   ` Sergei Shtylyov
2009-05-18  2:21 ` [PATCH 2/6] drivers/ide: Convert printk(KERN_INFO to pr_info( Joe Perches
2009-05-18  2:31   ` Joe Perches
2009-05-18  2:21 ` [PATCH 3/6] drivers/ide: Convert printk(KERN_ERR to pr_err( Joe Perches
2009-05-18  2:21 ` [PATCH 4/6] drivers/ide: Convert printk(KERN_WARNING to pr_warning( Joe Perches
2009-05-18  2:21 ` [PATCH 5/6] drivers/ide: Convert printk(KERN_CONT to pr_cont( Joe Perches
2009-05-18  2:21 ` [PATCH 6/6] drivers/ide: Convert printk(KERN_NOTICE to pr_notice( Joe Perches
2009-05-18 10:11   ` Sergei Shtylyov
2009-05-18 13:22     ` Krzysztof Halasa
2009-05-18 13:38       ` Sergei Shtylyov
2009-05-18 13:50       ` Bartlomiej Zolnierkiewicz
2009-05-18 17:18         ` Krzysztof Halasa
2009-05-18 18:55       ` Alan Cox
2009-05-18 13:32     ` Joe Perches
2009-05-18 14:12 ` [PATCH 0/6] drivers/ide Convert printk(KERN_<foo> to pr_<foo>( Bartlomiej Zolnierkiewicz
2009-05-18 15:41   ` Joe Perches
2009-05-18 15:48     ` Bartlomiej Zolnierkiewicz
2009-05-18 15:56     ` James Bottomley
2009-05-18 20:59       ` Joe Perches
2009-05-18 21:15         ` James Bottomley [this message]
2009-05-18 21:21           ` 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=1242681328.6347.38.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bzolnier@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).