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>,
Peter Zijlstra <peterz@infradead.org>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 4.12
Date: Tue, 2 May 2017 15:52:34 +0200 [thread overview]
Message-ID: <20170502135234.GC31170@pathway.suse.cz> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git for-linus
==========
- There is a situation when early console is not deregistered
because the preferred one matches a wrong entry. It caused
messages to appear twice.
This is 2nd attempt to fix it. The first one was wrong,
see the commit c6c7d83b9c9e6a8b3e6 ('Revert "console: don't
prefer first registered if DT specifies stdout-path"').
The fix is coupled with some small code clean up. Well,
the console registration code would deserve a big one.
We need to think about it.
- Do not lose information about the preemtive context when
the console semaphore is re-taken.
- Do not block CPU hotplug when someone else is already
pushing messages to the console.
----------------------------------------------------------------
Aleksey Makarov (3):
printk: fix name/type/scope of preferred_console var
printk: rename selected_console -> preferred_console
printk: fix double printing with earlycon
Petr Mladek (1):
printk: Correctly handle preemption in console_unlock()
Sergey Senozhatsky (1):
printk: use console_trylock() in console_cpu_notify()
kernel/printk/printk.c | 81 ++++++++++++++++++++++++++++++++++----------------
1 file changed, 56 insertions(+), 25 deletions(-)
Best Regards,
Petr Mladek
reply other threads:[~2017-05-02 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170502135234.GC31170@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=aleksey.makarov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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®