From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: [GIT PULL] printk for 5.11
Date: Mon, 14 Dec 2020 16:18:32 +0100 [thread overview]
Message-ID: <X9eCSHnMZyJUt3FW@alley> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.11
==============================
- Finally allow parallel writes and reads into/from the lockless
ringbuffer. But it is not a complete solution. Readers are still
serialized against each other. And nested writes are still
prevented by printk_safe per-CPU buffers.
- Use ttynull as the ultimate fallback for /dev/console.
- Officially allow to disable console output by using console="" or
console=null
- Few code cleanups.
==============================
We believe that the risk of logbuf_lock removal is small.
It is another important step in the printk rework. We are
moving slowly and carefully.
----------------------------------------------------------------
John Ogness (2):
printk: inline log_output(),log_store() in vprintk_store()
printk: remove logbuf_lock writer-protection of ringbuffer
Lukas Bulwahn (1):
printk: remove obsolete dead assignment
Nikolay Borisov (1):
printk: ringbuffer: Reference text_data_ring directly in callees.
Petr Mladek (4):
init/console: Use ttynull as a fallback when there is no console
printk/console: Allow to disable console output by using console="" or console=null
Merge branch 'for-5.11-null-console' into for-linus
Merge branch 'for-5.11' into for-linus
drivers/tty/Kconfig | 14 ---
drivers/tty/Makefile | 3 +-
drivers/tty/ttynull.c | 18 +++
include/linux/console.h | 3 +
init/main.c | 10 +-
kernel/printk/printk.c | 257 +++++++++++++++++++++++---------------
kernel/printk/printk_ringbuffer.c | 32 +++--
7 files changed, 200 insertions(+), 137 deletions(-)
next reply other threads:[~2020-12-14 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:18 Petr Mladek [this message]
2020-12-16 19:44 ` [GIT PULL] printk for 5.11 pr-tracker-bot
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=X9eCSHnMZyJUt3FW@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.thompson@linaro.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.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).