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 5.20 (sane changes)
Date: Thu, 4 Aug 2022 13:06:55 +0200 [thread overview]
Message-ID: <YuuoT1n6cosaVoiF@alley> (raw)
Hi Linus,
please pull the latest and only sane printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.20-sane
==================================
- Allow to read kernel log in gdb even on 32 bits systems.
- More granular check of the buffer usage in printf selftest.
- Clang warning fix.
==================================
I am going to be even more transparent when there is anything controversial
and discuss it in advance.
----------------------------------------------------------------
Antonio Borneo (1):
scripts/gdb: fix 'lx-dmesg' on 32 bits arch
Justin Stitt (1):
lib/test_printf.c: fix clang -Wformat warnings
Rasmus Villemoes (1):
lib/test_printf.c: split write-beyond-buffer check in two
lib/test_printf.c | 21 +++++++++++++++++----
scripts/gdb/linux/dmesg.py | 9 +++------
scripts/gdb/linux/utils.py | 14 ++++++++++++--
3 files changed, 32 insertions(+), 12 deletions(-)
next reply other threads:[~2022-08-04 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 11:06 Petr Mladek [this message]
2022-08-05 17:42 ` 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=YuuoT1n6cosaVoiF@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®