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>,
Peter Zijlstra <peterz@infradead.org>,
Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 6.13
Date: Mon, 18 Nov 2024 15:09:32 +0100 [thread overview]
Message-ID: <ZztKnBcca1OtwAcp@pathway.suse.cz> (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.13
=================================
- Print more precise information about the printk log buffer memory usage.
- Make sure that the sysrq title is shown on the console even
when deferred.
- Do not enable earlycon by `console=` which is meant to disable
the default console.
----------------------------------------------------------------
Arnd Bergmann (1):
printk: add dummy printk_force_console_enter/exit helpers
Isaac J. Manjarres (1):
printk: Improve memory usage logging during boot
Marcos Paulo de Souza (2):
printk: Introduce FORCE_CON flag
tty: sysrq: Use printk_force_console context on __handle_sysrq
Petr Mladek (1):
Merge branch 'for-6.13-force-console' into for-linus
Raul E Rangel (1):
init: Don't proxy `console=` to earlycon
drivers/tty/serial/earlycon.c | 23 +++++++++++++++++++++
drivers/tty/sysrq.c | 18 ++++++++---------
include/linux/printk.h | 11 ++++++++++
init/main.c | 5 +----
kernel/printk/internal.h | 3 +++
kernel/printk/printk.c | 47 ++++++++++++++++++++++++++++++++++---------
kernel/printk/printk_safe.c | 18 +++++++++++++++++
7 files changed, 102 insertions(+), 23 deletions(-)
next reply other threads:[~2024-11-18 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 14:09 Petr Mladek [this message]
2024-11-20 18:32 ` [GIT PULL] printk for 6.13 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=ZztKnBcca1OtwAcp@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--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=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 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.