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.16
Date: Tue, 2 Nov 2021 11:56:56 +0100 [thread overview]
Message-ID: <YYEZeIVxrp8MJ/yb@alley> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.16
=========================================
- Extend %pGp print format to print hex value of the page flags.
- Use kvmalloc instead of kmalloc to allocate devkmsg buffers.
- Misc cleanup and warning fixes.
----------------------------------------------------------------
Andy Shevchenko (1):
lib/vsprintf.c: Amend static asserts for format specifier flags
Arnd Bergmann (1):
printk: avoid -Wsometimes-uninitialized warning
John Ogness (1):
printk: use gnu_printf format attribute for printk_sprint()
Matthew Wilcox (Oracle) (5):
test_printf: Make pft array const
test_printf: Remove separate page_flags variable
test_printf: Remove custom appending of '|'
test_printf: Append strings more efficiently
vsprintf: Make %pGp print the hex value
Petr Mladek (2):
vsprintf: Update %pGp documentation about that it prints hex value
Merge branch 'for-5.16-vsprintf-pgp' into for-linus
Randy Dunlap (1):
ia64: don't do IA64_CMPXCHG_DEBUG without CONFIG_PRINTK
Yong-Taek Lee (1):
printk: use kvmalloc instead of kmalloc for devkmsg_user
Documentation/core-api/printk-formats.rst | 2 +-
arch/ia64/Kconfig.debug | 2 +-
kernel/printk/index.c | 5 +--
kernel/printk/printk.c | 5 ++-
lib/test_printf.c | 61 +++++++++++++------------------
lib/vsprintf.c | 11 +++++-
mm/debug.c | 2 +-
mm/memory-failure.c | 8 ++--
mm/page_owner.c | 4 +-
mm/slub.c | 4 +-
10 files changed, 51 insertions(+), 53 deletions(-)
next reply other threads:[~2021-11-02 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 10:56 Petr Mladek [this message]
2021-11-02 18:37 ` 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=YYEZeIVxrp8MJ/yb@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®