From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 6.1
Date: Wed, 5 Oct 2022 11:57:20 +0200 [thread overview]
Message-ID: <Yz1VANOUjskMbdxY@alley> (raw)
Hi Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-6.1
==============================================
- Initialize pointer hashing using the system workqueue. It avoids
taking locks in printk()/vsprintf() code path.
- Misc code clean up.
----------------------------------------------------------------
Jian Shen (1):
lib/vnsprintf: add const modifier for param 'bitmap'
Petr Mladek (2):
Merge branch 'for-6.1-hash-pointer-init' into for-linus
Merge branch 'rework/kthreads' into for-linus
Sebastian Andrzej Siewior (2):
lib/vsprintf: Remove static_branch_likely() from __ptr_to_hashval().
lib/vsprintf: Initialize vsprintf's pointer hash once the random core is ready.
Thomas Gleixner (5):
printk: Make pr_flush() static
printk: Declare log_wait properly
printk: Remove write only variable nr_ext_console_drivers
printk: Remove bogus comment vs. boot consoles
printk: Mark __printk percpu data ready __ro_after_init
fs/proc/kmsg.c | 2 --
include/linux/printk.h | 7 -------
include/linux/syslog.h | 3 +++
kernel/printk/printk.c | 19 ++++---------------
lib/vsprintf.c | 51 +++++++++++++++++++++++++++-----------------------
5 files changed, 35 insertions(+), 47 deletions(-)
next reply other threads:[~2022-10-05 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 9:57 Petr Mladek [this message]
2022-10-10 18:48 ` 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=Yz1VANOUjskMbdxY@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®