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>,
linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [GIT PULL] printk for 5.10 (includes lockless ringbuffer)
Date: Fri, 27 Nov 2020 14:47:15 +0100 [thread overview]
Message-ID: <X8EDY+hYkuyja5vy@alley> (raw)
Linus,
please pull a printk hotfix from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.10-rc6-fixup
=========================
- Do not lose trailing newline in pr_cont() calls.
- Two trivial fixes: dead-store and a config description.
=========================
PS: I do not have much experience with pushing fixes this late
in the release cycle.
I push the important fix even before it has reached linux-next.
The fix is straightforward and trivial. And it looks better to have
it in rc6 than in the potentially last one rc7.
Also I added the two trivial fixes that I queued few weeks ago.
They were trivial enough to get pushed at any time. And they
fixed something that was introduced in 5.10-rc1.
Feel free to postpone this for rc7 or take only the one fix
of the newlines handling.
----------------------------------------------------------------
John Ogness (1):
printk: finalize records with trailing newlines
Lukas Bulwahn (1):
printk: remove unneeded dead-store assignment
Paul Menzel (1):
init/Kconfig: Fix CPU number in LOG_CPU_MAX_BUF_SHIFT description
Petr Mladek (1):
Merge branch 'for-5.10-pr_cont-fixup' into for-linus
init/Kconfig | 2 +-
kernel/printk/printk.c | 4 ++--
kernel/printk/printk_ringbuffer.c | 2 --
3 files changed, 3 insertions(+), 5 deletions(-)
next reply other threads:[~2020-11-27 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 13:47 Petr Mladek [this message]
2020-11-27 19:19 ` [GIT PULL] printk for 5.10 (includes lockless ringbuffer) pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-10-16 15:05 Petr Mladek
2020-10-16 19:54 ` pr-tracker-bot
2020-10-12 14:49 Petr Mladek
2020-10-13 23:49 ` pr-tracker-bot
2020-10-14 14:16 ` Geert Uytterhoeven
2020-10-14 14:58 ` Rasmus Villemoes
2020-10-14 15:07 ` Geert Uytterhoeven
2020-10-15 8:03 ` Petr Mladek
2020-10-14 20:55 ` John Ogness
2020-10-15 7:52 ` Petr Mladek
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=X8EDY+hYkuyja5vy@alley \
--to=pmladek@suse.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=wangkefeng.wang@huawei.com \
/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).