From: John Ogness <john.ogness@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <wang.yi59@zte.com.cn>, <pmladek@suse.com>,
<sergey.senozhatsky@gmail.com>, <rostedt@goodmis.org>,
<linux-kernel@vger.kernel.org>, <xue.zhihong@zte.com.cn>,
<jiang.xuexin@zte.com.cn>, <wang.yong12@zte.com.cn>,
linux-rt-users@vger.kernel.org
Subject: Re: [RT PATCH] Fixed: line break of pr_cont not take effect
Date: Sat, 23 May 2020 12:41:27 +0200 [thread overview]
Message-ID: <87imgnndbc.fsf_-_@vostro.fn.ogness.net> (raw)
In-Reply-To: <202005231419598080913@zte.com.cn> (wang's message of "Sat, 23 May 2020 14:19:59 +0800 (CST)")
Thank you. I added Sebastian Siewior and linux-rt-users to the addresses
since this is a patch against PREEMPT_RT.
On 2020-05-23, <wang.yi59@zte.com.cn> wrote:
> Line break of pr_cont not take effect.
> Use several pr_cont to print continuous paragraph, it is expected to
> have line break when line ends up with '\n', however the paragraph
> does not have line break
> -printk_kthread_func will not print info before log_store insert msg
> into printk_rb, and pr_cont calls cont_add to keep data in buffer.
> cont_add only when the following conditions are met insert msg to
> printk_rb
> 1.cpu != c->cpu_owner || !(flags & LOG_CONT)
> 2.c->len + len > sizeof(c->buf)
>
> Signed-off-by: 汪勇10269566 <wang.yong12@zte.com.cn>
Acked-by: John Ogness <john.ogness@linutronix.de>
@Sebastian: The original patch submission is here[0].
Thanks,
John Ogness
[0] https://lkml.kernel.org/r/1590025064-14433-1-git-send-email-wang.yi59@zte.com.cn
next parent reply other threads:[~2020-05-23 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202005231419598080913@zte.com.cn>
2020-05-23 10:41 ` John Ogness [this message]
2020-05-26 16:44 ` [RT PATCH] Fixed: line break of pr_cont not take effect Sebastian Andrzej Siewior
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=87imgnndbc.fsf_-_@vostro.fn.ogness.net \
--to=john.ogness@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=wang.yi59@zte.com.cn \
--cc=wang.yong12@zte.com.cn \
--cc=xue.zhihong@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).