mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Toshiaki Yamane <yamanetoshi@gmail.com>
Cc: greg@kroah.com, willy@meta-x.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] panel: Use pr_debug(...) rather than printk(KERN_DEBUG ...)
Date: Tue, 10 Jul 2012 13:58:37 -0700	[thread overview]
Message-ID: <1341953917.6118.165.camel@joe2Laptop> (raw)
In-Reply-To: <1341919338-8800-1-git-send-email-yamanetoshi@gmail.com>

On Tue, 2012-07-10 at 20:22 +0900, Toshiaki Yamane wrote:
> This change is inspired by checkpatch.
[]
> diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/panel.c
[]
> @@ -1838,9 +1838,8 @@ static void panel_process_inputs(void)
>  	struct logical_input *input;
>  
>  #if 0
> -	printk(KERN_DEBUG
> -	       "entering panel_process_inputs with pp=%016Lx & pc=%016Lx\n",
> -	       phys_prev, phys_curr);
> +	pr_debug("entering panel_process_inputs with pp=%016Lx & pc=%016Lx\n",
> +		 phys_prev, phys_curr);
>  #endif

Might as well delete these #if 0 blocks instead

>  
>  	keypressed = 0;
> @@ -2003,8 +2002,8 @@ static struct logical_input *panel_bind_key(char *name, char *press,
>  	key->fall_time = 1;
>  
>  #if 0
> -	printk(KERN_DEBUG "bind: <%s> : m=%016Lx v=%016Lx\n", name, key->mask,
> -	       key->value);
> +	pr_debug("bind: <%s> : m=%016Lx v=%016Lx\n", name, key->mask,
> +		 key->value);
>  #endif
>  	strncpy(key->u.kbd.press_str, press, sizeof(key->u.kbd.press_str));
>  	strncpy(key->u.kbd.repeat_str, repeat, sizeof(key->u.kbd.repeat_str));





      parent reply	other threads:[~2012-07-11  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 11:22 Toshiaki Yamane
2012-07-10 11:24 ` [PATCH 2/3] panel: Use pr_info(...) rather than printk(KERN_INFO ...) Toshiaki Yamane
2012-07-10 11:25 ` [PATCH 3/3] panel: Use pr_err(...) rather than printk(KERN_ERR ...) Toshiaki Yamane
2012-07-10 20:59   ` Joe Perches
2012-07-10 20:58 ` Joe Perches [this message]

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=1341953917.6118.165.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@meta-x.org \
    --cc=yamanetoshi@gmail.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

all inboxes | Powered by JetHome®