mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Joe Perches <joe@perches.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	linux-kernel@vger.kernel.org, bleong@codeaurora.org
Subject: Re: [PATCH 1/2] drivers: regulator: core: use pr_fmt
Date: Thu, 18 Nov 2010 10:37:58 +0000	[thread overview]
Message-ID: <20101118103758.GB7233@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1290040508.16344.532.camel@c-dwalke-linux.qualcomm.com>

On Wed, Nov 17, 2010 at 04:35:08PM -0800, Daniel Walker wrote:
> On Wed, 2010-11-17 at 16:29 -0800, Joe Perches wrote:

> > > +			pr_err("%s '%s' voltage constraints\n", "invalid",
> > > +				name);

> > Using a separate pointer for invalid and unsupportable
> > doesn't save much text space and is very hard to grep.

> > I think it's more intelligible as:

> > 			pr_err("%s: Invalid voltage constraints\n", name);

> I noticed that also, but I didn't feel like changing it when I did this.

This is some stuff from David Brownell which slipped through in review
and should be removed to just have the string.  His theory is that this
allows the compiler to merge multiple versions of the format string,
resulting in a space saving but given how trivial the saving is and the
impact on legibility it's really not worth it.

>                         printk(KERN_WARNING "%s: could not add regulator_dev"
>                                 " load sysfs\n", __func__);

> I'm not sure what this one was suppose to say.

That's a different thing - someone's just split the string over multiple
lines - the two strings will just be concatenated.

  reply	other threads:[~2010-11-18 10:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 23:30 Daniel Walker
2010-11-17 23:30 ` [PATCH 2/2] drivers: regulator: core: convert to using pr_ macros Daniel Walker
2010-11-18  0:36   ` Joe Perches
2010-11-18  1:30     ` Joe Perches
2010-11-18 13:30       ` Mark Brown
2010-11-18 13:29     ` Mark Brown
2010-11-18 16:29       ` Joe Perches
2010-11-18  0:29 ` [PATCH 1/2] drivers: regulator: core: use pr_fmt Joe Perches
2010-11-18  0:35   ` Daniel Walker
2010-11-18 10:37     ` Mark Brown [this message]
2010-11-18 16:44       ` Joe Perches
2010-11-18 10:35 ` Mark Brown
2010-11-19 11:09   ` Liam Girdwood
2010-11-19 17:07     ` 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=20101118103758.GB7233@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=bleong@codeaurora.org \
    --cc=dwalker@codeaurora.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    /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

Powered by JetHome