mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.15
Date: Thu, 27 Mar 2025 11:59:11 +0100	[thread overview]
Message-ID: <Z-Uvf8YsA6q54hv4@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.15

==============================================

- New option "printk.debug_non_panic_cpus" allows to store printk
  messages from non-panic CPUs during panic. It might be useful
  when panic() fails. It is disabled by default because it increases
  the chance to see the messages printed before panic() and on
  the panic-CPU.

- New build option "CONFIG_NULL_TTY_DEFAULT_CONSOLE" allows to build
  kernel without the virtual terminal support which prefers ttynull
  over serial console.

- Do not unblank suspended consoles.

- Some code clean up.

----------------------------------------------------------------
Adam Simonelli (1):
      printk: Add an option to allow ttynull to be a default console device

Donghyeok Choe (1):
      printk/panic: Add option to allow non-panic CPUs to write to the ring buffer.

Marcos Paulo de Souza (5):
      printk: Rename suspend_console to console_suspend_all
      printk: Rename resume_console to console_resume_all
      printk: Rename console_stop to console_suspend
      printk: Rename console_start to console_resume
      printk: Check CON_SUSPEND when unblanking a console

Petr Mladek (1):
      Merge branch 'for-6.15-console-suspend-api-cleanup' into for-linus

 Documentation/admin-guide/kernel-parameters.txt    |  8 ++++
 Documentation/admin-guide/serial-console.rst       |  4 +-
 drivers/gpu/drm/clients/drm_log.c                  |  4 +-
 drivers/tty/Kconfig                                | 19 +++++++-
 drivers/tty/serial/serial_core.c                   |  6 +--
 include/linux/console.h                            |  8 ++--
 kernel/kexec_core.c                                |  4 +-
 kernel/power/hibernate.c                           | 16 +++----
 kernel/power/suspend.c                             |  8 ++--
 kernel/printk/internal.h                           |  1 +
 kernel/printk/printk.c                             | 55 +++++++++++++++++-----
 kernel/printk/printk_ringbuffer.c                  | 13 +++--
 .../pm-graph/config/custom-timeline-functions.cfg  |  4 +-
 tools/power/pm-graph/sleepgraph.py                 |  6 +--
 14 files changed, 110 insertions(+), 46 deletions(-)

             reply	other threads:[~2025-03-27 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 10:59 Petr Mladek [this message]
2025-03-28  2:31 ` 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=Z-Uvf8YsA6q54hv4@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 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®