From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
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>,
linux-kernel@vger.kernel.org,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: [GIT PULL] printk for 5.9
Date: Tue, 4 Aug 2020 19:12:09 +0200 [thread overview]
Message-ID: <20200804171209.GF24529@alley> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux tags/printk-for-5.9
===============================
- Herbert Xu made printk header file self-contained.
- Andy Shevchenko and Sergey Senozhatsky cleaned up console->setup()
error handling.
- Andy Shevchenko did some cleanups (e.g. sparse warning) in vsprintf code.
- Minor documentation updates.
===============================
The patch from Herbert Xu, fixing an include hell, caused some build
breakages in linux-next. All of those were resolved, the fixup patches
landed in tip/locking tree (which you have pulled already), so everything
should be fine now.
----------------------------------------------------------------
Alexander A. Klimov (1):
Replace HTTP links with HTTPS ones: vsprintf
Andy Shevchenko (9):
mips: Return proper error code from console ->setup() hook
serial: sunsab: Return proper error code from console ->setup() hook
serial: sunzilog: Return proper error code from console ->setup() hook
tty: hvc: Return proper error code from console ->setup() hook
console: Propagate error code from console ->setup()
console: Fix trivia typo 'change' -> 'chance'
lib/vsprintf: Replace hidden BUILD_BUG_ON() with static_assert()
lib/vsprintf: Replace custom spec to print decimals with generic one
lib/vsprintf: Force type of flags value for gfp_t
Bruno Meneguele (1):
doc:kmsg: explicitly state the return value in case of SEEK_CUR
Herbert Xu (1):
printk: Make linux/printk.h self-contained
Petr Mladek (1):
Merge branch 'for-5.9-console-return-codes' into for-linus
Sergey Senozhatsky (1):
hvc: unify console setup naming
Documentation/ABI/testing/dev-kmsg | 11 ++++++++
Documentation/core-api/printk-formats.rst | 4 +--
arch/mips/fw/arc/arc_con.c | 4 ++-
arch/s390/include/asm/bug.h | 2 +-
drivers/tty/hvc/hvc_xen.c | 4 +--
drivers/tty/hvc/hvsi.c | 2 +-
drivers/tty/serial/sunsab.c | 2 +-
drivers/tty/serial/sunzilog.c | 2 +-
include/linux/printk.h | 1 +
include/linux/ratelimit.h | 36 +-------------------------
include/linux/ratelimit_types.h | 43 +++++++++++++++++++++++++++++++
kernel/printk/printk.c | 16 +++++++++---
lib/vsprintf.c | 17 +++++-------
13 files changed, 86 insertions(+), 58 deletions(-)
create mode 100644 include/linux/ratelimit_types.h
next reply other threads:[~2020-08-04 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 17:12 Petr Mladek [this message]
2020-08-05 6:05 ` 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=20200804171209.GF24529@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.thompson@linaro.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--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®