All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hema Prathaban <hemaklnce@gmail.com>
Cc: devel@driverdev.osuosl.org, oleg.drokin@intel.com,
	andreas.dilger@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: lustre: libcfs: pr_warn instead printk
Date: Fri, 15 Aug 2014 16:21:48 -0700	[thread overview]
Message-ID: <20140815232148.GA10600@kroah.com> (raw)
In-Reply-To: <20140815181805.GA4709@hema-Inspiron-3520>

On Fri, Aug 15, 2014 at 11:48:05PM +0530, Hema Prathaban wrote:
> This patch fixes the following warning using checkpatch.pl
> WARNING: Prefer [subsystem eg: netdev]_warn([subsystem]dev, ... then
> dev_warn(dev, ... then pr_warn(...  to printk(KERN_WARNING ...
> 
> Signed-off-by: Hema Prathaban <hemaklnce@gmail.com>
> ---
>  drivers/staging/lustre/lustre/libcfs/debug.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/lustre/lustre/libcfs/debug.c b/drivers/staging/lustre/lustre/libcfs/debug.c
> index 6b58469..8143ebe 100644
> --- a/drivers/staging/lustre/lustre/libcfs/debug.c
> +++ b/drivers/staging/lustre/lustre/libcfs/debug.c
> @@ -344,7 +344,7 @@ void libcfs_debug_dumplog_internal(void *arg)
>  		snprintf(debug_file_name, sizeof(debug_file_name) - 1,
>  			 "%s.%ld.%ld", libcfs_debug_file_path_arr,
>  			 get_seconds(), (long_ptr_t)arg);
> -		printk(KERN_ALERT "LustreError: dumping log to %s\n",
> +		pr_alert(KERN_ALERT "LustreError: dumping log to %s\n",
>  		       debug_file_name);
>  		cfs_tracefile_dump_all_pages(debug_file_name);
>  		libcfs_run_debug_log_upcall(debug_file_name);
> @@ -376,7 +376,7 @@ void libcfs_debug_dumplog(void)
>  			     (void *)(long)current_pid(),
>  			     "libcfs_debug_dumper");
>  	if (IS_ERR(dumper))
> -		printk(KERN_ERR "LustreError: cannot start log dump thread:"
> +		pr_err(KERN_ERR "LustreError: cannot start log dump thread:"

You need to take the printk prefix off of these types of lines if you
are using the pr_*() macro, otherwise you will get a mess in the system
log.

thanks,

greg k-h

  reply	other threads:[~2014-08-15 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 18:18 [PATCH] staging: lustre: lustre: libcfs: pr_warn instead printk Hema Prathaban
2014-08-15 23:21 ` Greg KH [this message]
2014-08-16 18:40   ` Hema .p

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=20140815232148.GA10600@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hemaklnce@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.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.