From: Joe Perches <joe@perches.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] kernel/debug/debug_core.c: Logging clean-up
Date: Thu, 12 Jun 2014 12:04:01 -0700 [thread overview]
Message-ID: <1402599841.12385.20.camel@joe-AO725> (raw)
In-Reply-To: <1402598918-5729-1-git-send-email-fabf@skynet.be>
On Thu, 2014-06-12 at 20:48 +0200, Fabian Frederick wrote:
> -Convert printk( to pr_foo()
> -Add pr_fmt
> -Coalesce formats
Might as well add missing newlines
and maybe remove unnecessary periods.
> diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
[]
> @@ -196,8 +199,8 @@ int __weak kgdb_validate_break_address(unsigned long addr)
> return err;
> err = kgdb_arch_remove_breakpoint(&tmp);
> if (err)
> - printk(KERN_ERR "KGDB: Critical breakpoint error, kernel "
> - "memory destroyed at: %lx", addr);
> + pr_err("Critical breakpoint error, kernel memory destroyed at: %lx",
> + addr);
Add '\n' newline
[]
> @@ -256,8 +259,8 @@ int dbg_activate_sw_breakpoints(void)
> error = kgdb_arch_set_breakpoint(&kgdb_break[i]);
> if (error) {
> ret = error;
> - printk(KERN_INFO "KGDB: BP install failed: %lx",
> - kgdb_break[i].bpt_addr);
> + pr_info("BP install failed: %lx",
> + kgdb_break[i].bpt_addr);
here too
> @@ -964,8 +966,7 @@ int kgdb_register_io_module(struct kgdb_io *new_dbg_io_ops)
> if (dbg_io_ops) {
> spin_unlock(&kgdb_registration_lock);
>
> - printk(KERN_ERR "kgdb: Another I/O driver is already "
> - "registered with KGDB.\n");
> + pr_err("Another I/O driver is already registered with KGDB.\n");
Maybe remove period
pr_err("Another I/O driver is already registered with KGDB\n");
> @@ -981,8 +982,7 @@ int kgdb_register_io_module(struct kgdb_io *new_dbg_io_ops)
>
> spin_unlock(&kgdb_registration_lock);
>
> - printk(KERN_INFO "kgdb: Registered I/O driver %s.\n",
> - new_dbg_io_ops->name);
> + pr_info("Registered I/O driver %s.\n", new_dbg_io_ops->name);
here too
> @@ -1017,8 +1017,7 @@ void kgdb_unregister_io_module(struct kgdb_io *old_dbg_io_ops)
>
> spin_unlock(&kgdb_registration_lock);
>
> - printk(KERN_INFO
> - "kgdb: Unregistered I/O driver %s, debugger disabled.\n",
> + pr_info("Unregistered I/O driver %s, debugger disabled.\n",
> old_dbg_io_ops->name);
and here
prev parent reply other threads:[~2014-06-12 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 18:48 [PATCH 1/1] kernel/debug/debug_core.c: Logging clean-up Fabian Frederick
2014-06-12 18:58 ` Jason Wessel
2014-06-12 19:04 ` 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=1402599841.12385.20.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=jason.wessel@windriver.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