The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	jbaron@redhat.com
Subject: Re: [PATCH 2/3] params: replace printk(KERN_<LVL>...) with pr_<lvl>(...)
Date: Thu, 03 May 2012 11:50:41 -0700	[thread overview]
Message-ID: <1336071041.13866.39.camel@joe2Laptop> (raw)
In-Reply-To: <1336067860-19953-2-git-send-email-jim.cromie@gmail.com>

On Thu, 2012-05-03 at 11:57 -0600, Jim Cromie wrote:
> I left 1 printk which uses __FILE__, __LINE__ explicitly, which should
> not be subject to generic preferences expressed via pr_fmt().
> 
> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
> ---
>  kernel/params.c |   33 ++++++++++++---------------------
>  1 files changed, 12 insertions(+), 21 deletions(-)
> 
> diff --git a/kernel/params.c b/kernel/params.c
> index be78c90..08414ba 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -201,25 +201,21 @@ int parse_args(const char *doing,
>  		irq_was_disabled = irqs_disabled();
>  		ret = parse_one(param, val, doing, params, num,
>  				min_level, max_level, unknown);
> -		if (irq_was_disabled && !irqs_disabled()) {
> -			printk(KERN_WARNING "parse_args(): option '%s' enabled "
> -					"irq's!\n", param);
> -		}
> +		if (irq_was_disabled && !irqs_disabled())
> +			pr_warn("option '%s' enabled irq's!\n", param);
> +

The other parse_args pr_<level> uses have
	'"%s: ...", doing, ...'.
Maybe this one should too.

>  		switch (ret) {
>  		case -ENOENT:
> -			printk(KERN_ERR "%s: Unknown parameter `%s'\n",
> -			       doing, param);
> +			pr_err("%s: Unknown parameter `%s'\n", doing, param);
>  			return ret;
[]
> @@ -753,11 +746,9 @@ static struct module_kobject * __init locate_module_kobject(const char *name)
>  #endif
>  		if (err) {
>  			kobject_put(&mk->kobj);
> -			printk(KERN_ERR
> -				"Module '%s' failed add to sysfs, error number %d\n",
> +			pr_err("Module '%s' failed add to sysfs, error: %d\n"
> +				"The system will be unstable now.\n",
>  				name, err);
> -			printk(KERN_ERR
> -				"The system will be unstable now.\n");
>  			return NULL;
>  		}
>  

It'd be nice to align the arguments and perhaps a
single line output may be better.

Maybe something like:

			pr_err("Adding module '%s' to sysfs failed (%d), the system is unstable\n",
			       name, err);

though perhaps this should be pr_crit
if it's really unstable.


  reply	other threads:[~2012-05-03 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 17:57 [PATCH 1/3] params.c: fix Smack complaint about parse_args Jim Cromie
2012-05-03 17:57 ` [PATCH 2/3] params: replace printk(KERN_<LVL>...) with pr_<lvl>(...) Jim Cromie
2012-05-03 18:50   ` Joe Perches [this message]
2012-05-03 17:57 ` [PATCH 3/3] dynamic_debug: remove unneeded includes Jim Cromie
2012-05-05  4:36   ` Stephen Rothwell
2012-05-05  5:52     ` Jim Cromie
2012-05-05  6:08       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2012-05-03 19:12 [PATCH 2/3] params: replace printk(KERN_<LVL>...) with pr_<lvl>(...) Jim Cromie
2012-05-03 19:23 ` Joe Perches
2012-05-04  0:22 Jim Cromie

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=1336071041.13866.39.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@redhat.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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