mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Joe Perches <joe@perches.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org, bleong@codeaurora.org
Subject: Re: [PATCH 1/2] drivers: regulator: core: use pr_fmt
Date: Wed, 17 Nov 2010 16:35:08 -0800	[thread overview]
Message-ID: <1290040508.16344.532.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <1290040194.28741.324.camel@Joe-Laptop>

On Wed, 2010-11-17 at 16:29 -0800, Joe Perches wrote:
> On Wed, 2010-11-17 at 15:30 -0800, Daniel Walker wrote:
> > This adds a pr_fmt line which uses the __func__ macro. I also
> > convert the current pr_ lines to remove their __func__ usage.
> []
> > diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> > @@ -765,8 +767,8 @@ static int machine_constraints_voltage(struct regulator_dev *rdev,
> >  
> >  		/* else require explicit machine-level constraints */
> >  		if (cmin <= 0 || cmax <= 0 || cmax < cmin) {
> > -			pr_err("%s: %s '%s' voltage constraints\n",
> > -				       __func__, "invalid", name);
> > +			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.


there is another one here,

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

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

Daniel


-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


  reply	other threads:[~2010-11-18  0:35 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 [this message]
2010-11-18 10:37     ` Mark Brown
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=1290040508.16344.532.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=bleong@codeaurora.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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