All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 4.13
Date: Mon, 3 Jul 2017 16:24:34 +0200	[thread overview]
Message-ID: <20170703142434.GV1538@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


==========

- Store printk() messages into the main log buffer directly even in NMI
  when the lock is available. It is the best effort to print even large
  chunk of text. It is handy, for example, when all ftrace messages
  are printed during the system panic in NMI.

- Add missing annotations to calm down compiler warnings.

----------------------------------------------------------------

Nicolas Iooss (1):
      printk: add __printf attributes to internal functions

Petr Mladek (2):
      printk: Use the main logbuf in NMI when logbuf_lock is available
      Merge branch 'for-4.13' into for-linus

 kernel/printk/internal.h    |  6 ++++--
 kernel/printk/printk.c      | 19 ++++++++++++++-----
 kernel/printk/printk_safe.c | 36 +++++++++++++++++++++++++++++-------
 lib/nmi_backtrace.c         |  3 +++
 4 files changed, 50 insertions(+), 14 deletions(-)


Best Regards,
Petr Mladek

             reply	other threads:[~2017-07-03 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 14:24 Petr Mladek [this message]
2017-07-05 18:23 ` [GIT PULL] printk for 4.13 Linus Torvalds
2017-07-06  0:44   ` Sergey Senozhatsky
2017-07-06  0:53     ` Sergey Senozhatsky
2017-07-06  1:15     ` Linus Torvalds
2017-07-06  1:18       ` Sergey Senozhatsky

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=20170703142434.GV1538@pathway.suse.cz \
    --to=pmladek@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.