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>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 5.17
Date: Mon, 10 Jan 2022 15:33:50 +0100	[thread overview]
Message-ID: <YdxDzgijikydIwOP@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-5.17

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

- Remove some twists in the console registration code. It does not change
  the existing behavior except for one corner case. The proper default
  console (with tty binding) will be registered again even when it has
  been removed in the meantime. It is actually a bug fix. Anyway, this
  modified behavior requires some manual interaction.

- Optimize gdb extension for huge ring buffers.

- Do not use atomic operations for a local bitmap variable.

- Update git links in MAINTAINERS.

----------------------------------------------------------------
Christophe JAILLET (1):
      vsprintf: Use non-atomic bitmap API when applicable

John Ogness (1):
      scripts/gdb: lx-dmesg: read records individually

Petr Mladek (8):
      printk/console: Split out code that enables default console
      printk/console: Rename has_preferred_console to need_default_console
      printk/console: Remove unnecessary need_default_console manipulation
      printk/console: Remove need_default_console variable
      printk/console: Clean up boot console handling in register_console()
      MAINTAINERS/vsprintf: Update link to printk git tree
      MAINTAIERS/printk: Add link to printk git
      Merge branch 'console-registration-cleanup' into for-linus

 MAINTAINERS                |   3 +-
 kernel/printk/printk.c     | 104 +++++++++++++++++++++++++--------------------
 lib/vsprintf.c             |   4 +-
 scripts/gdb/linux/dmesg.py |  35 +++++++--------
 4 files changed, 80 insertions(+), 66 deletions(-)

             reply	other threads:[~2022-01-10 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 14:33 Petr Mladek [this message]
2022-01-11 18:03 ` 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=YdxDzgijikydIwOP@alley \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --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®