linux-kernel.vger.kernel.org archive mirror
 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>,
	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.6
Date: Mon, 4 Sep 2023 12:16:57 +0200	[thread overview]
Message-ID: <ZPWumSQVlzdYkSJJ@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.6

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

- Do not try to get the console lock when it is not need or useful
  in panic().

- Replace the global console_suspended state by a per-console flag.

- Export symbols needed for dumping the raw printk buffer in panic().

- Fix documentation of printf formats for integer types.

- Moved Sergey Senozhatsky to the reviewer role.

- Misc cleanups.

----------------------------------------------------------------
Andy Shevchenko (2):
      docs: printk-formats: Fix hex printing of signed values
      docs: printk-formats: Treat char as always unsigned

Enlin Mu (1):
      printk: export symbols for debug modules

John Ogness (7):
      kdb: Do not assume write() callback available
      printk: Reduce console_unblank() usage in unsafe scenarios
      printk: Keep non-panic-CPUs out of console lock
      printk: Do not take console lock for console_flush_on_panic()
      printk: Consolidate console deferred printing
      printk: Add per-console suspended state
      printk: Rename abandon_console_lock_in_panic() to other_cpu_in_panic()

Kees Cook (1):
      printk: ringbuffer: Fix truncating buffer size min_t cast

Nathan Chancellor (1):
      lib: test_scanf: Add explicit type cast to result initialization in test_number_prefix()

Petr Mladek (2):
      Merge branch 'for-6.6-vsprintf-doc' into for-linus
      Merge branch 'rework/misc-cleanups' into for-linus

Sergey Senozhatsky (1):
      MAINTAINERS: adjust printk/vsprintf entries

 Documentation/core-api/printk-formats.rst |   9 +-
 MAINTAINERS                               |   4 +-
 include/linux/console.h                   |   3 +
 kernel/debug/kdb/kdb_io.c                 |   2 +
 kernel/printk/internal.h                  |   2 +
 kernel/printk/printk.c                    | 215 +++++++++++++++++++++---------
 kernel/printk/printk_ringbuffer.c         |   2 +-
 kernel/printk/printk_safe.c               |   9 +-
 lib/test_scanf.c                          |   2 +-
 9 files changed, 167 insertions(+), 81 deletions(-)

             reply	other threads:[~2023-09-04 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 10:16 Petr Mladek [this message]
2023-09-04 21:13 ` [GIT PULL] printk for 6.6 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=ZPWumSQVlzdYkSJJ@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;
as well as URLs for NNTP newsgroup(s).