From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Joe Perches <joe@perches.com>, Jiri Kosina <jikos@kernel.org>,
Theodore Tso <tytso@mit.edu>, Hannes Reinecke <hare@suse.de>,
Jan Kara <jack@suse.com>, Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)
Date: Fri, 4 Nov 2016 03:01:31 +0900 [thread overview]
Message-ID: <20161103180131.GC423@swordfish> (raw)
In-Reply-To: <20161103173153.GA423@swordfish>
fix a typo
On (11/04/16 02:31), Sergey Senozhatsky wrote:
[..]
> #4 console semaphore
> discussion outcome:
> we agreed that we can do better here and that it makes sense to do
^^^^ IOW, console semaphore thing
can be improved
> what's been proposed in my slides. but, I keep it as a low priority.
> frankly. I'd be happy to see #1-#3 in the mainline in 9-12 months.
^^^^ #1-#2, of course. but #1 consists
of 2 steps.
I'm still not entirely sure if I want to split async pintk and printk
deadlock rework. these things want to come together, for a number of
reasons. or, at least, push the async printk before printk deadlock
rework.
-ss
next prev parent reply other threads:[~2016-11-03 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1478106396.23018.51.camel@perches.com>
2016-11-03 17:31 ` printk considered harmful (was: [TECH TOPIC] asynchronous printk) Sergey Senozhatsky
2016-11-03 18:01 ` Sergey Senozhatsky [this message]
2016-11-03 23:28 ` Jan Kara
2016-11-04 16:07 ` 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=20161103180131.GC423@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=hare@suse.de \
--cc=jack@suse.com \
--cc=jikos@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.