From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.com>, Tejun Heo <tj@kernel.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org,
Byungchul Park <byungchul.park@lge.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v12 0/3] printk: Make printk() completely async
Date: Wed, 29 Jun 2016 14:32:07 +0900 [thread overview]
Message-ID: <20160629053207.GA522@swordfish> (raw)
In-Reply-To: <1467177404.24287.99.camel@perches.com>
On (06/28/16 22:16), Joe Perches wrote:
> On Wed, 2016-06-29 at 14:08 +0900, Sergey Senozhatsky wrote:
> > the patch to fix the async KERN_CONT printk regression I mentioned
> > several days ago in another thread.
>
> KERN_CONT is effectively a no-op.
> This is any printk without a KERN_<LEVEL>
if the message has no LOG_NEWLINE in flags then it's stored as LOG_CONT
in log buffer, but before getting there it sits in cont buffer. and those
are usually KERN_CONT messages that don't have LOG_NEWLINE in flags. may
be the wording is not exactly correct in the original message.
-ss
next prev parent reply other threads:[~2016-06-29 5:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 13:18 [PATCH v12 0/3] printk: Make printk() completely async Sergey Senozhatsky
2016-05-13 13:18 ` [PATCH v12 1/3] " Sergey Senozhatsky
2016-05-13 13:18 ` [PATCH v12 2/3] printk: Make wake_up_klogd_work_func() async Sergey Senozhatsky
2016-05-13 13:18 ` [PATCH v12 3/3] printk: make printk.synchronous param rw Sergey Senozhatsky
2016-06-09 2:20 ` [PATCH v12 0/3] printk: Make printk() completely async Sergey Senozhatsky
2016-06-29 5:08 ` Sergey Senozhatsky
2016-06-29 5:16 ` Joe Perches
2016-06-29 5:32 ` Sergey Senozhatsky [this message]
2016-07-12 16:28 ` Petr Mladek
2016-07-13 7:42 ` Sergey Senozhatsky
2016-07-13 11:14 ` Petr Mladek
2016-07-13 13:24 ` Sergey Senozhatsky
2016-07-13 14:22 ` Petr Mladek
2016-07-11 19:25 ` Viresh Kumar
2016-07-12 15:59 ` Petr Mladek
2016-07-12 16:46 ` Sergey Senozhatsky
2016-07-12 17:04 ` Viresh Kumar
2016-07-13 11:19 ` Petr Mladek
-- strict thread matches above, loose matches on Subject: below --
2016-04-22 13:52 Sergey Senozhatsky
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=20160629053207.GA522@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul.park@lge.com \
--cc=jack@suse.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).