From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: zhe.he@windriver.com
Cc: pmladek@suse.com, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] printk: Add KBUILD_MODNAME
Date: Sun, 30 Sep 2018 01:05:22 +0900 [thread overview]
Message-ID: <20180929160522.GA573@tigerII.localdomain> (raw)
In-Reply-To: <1538232529-72706-3-git-send-email-zhe.he@windriver.com>
On (09/29/18 22:48), zhe.he@windriver.com wrote:
>
> +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> +
Plus this one
---
kernel/printk/printk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index c9068074dd09..e32f93a2fa84 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2732,7 +2732,7 @@ void register_console(struct console *newcon)
if (newcon->flags & CON_EXTENDED)
if (!nr_ext_console_drivers++)
- pr_info("printk: continuation disabled due to ext consoles, expect more fragments in /dev/kmsg\n");
+ pr_info("continuation disabled due to ext consoles, expect more fragments in /dev/kmsg\n");
if (newcon->flags & CON_PRINTBUFFER) {
/*
---
-ss
next prev parent reply other threads:[~2018-09-29 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 14:48 [PATCH v4 1/4] printk: Fix panic caused by passing log_buf_len to command line zhe.he
2018-09-29 14:48 ` [PATCH v4 2/4] printk: Correct wrong casting zhe.he
2018-09-29 14:48 ` [PATCH v4 3/4] printk: Add KBUILD_MODNAME zhe.he
2018-09-29 16:05 ` Sergey Senozhatsky [this message]
2018-09-29 14:48 ` [PATCH v4 4/4] printk: Give error on attempt to set log buffer length to over 4G zhe.he
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=20180929160522.GA573@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=zhe.he@windriver.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
Powered by JetHome