From: Joe Perches <joe@perches.com>
To: Steven Rostedt <srostedt@redhat.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: printk discussions at KS
Date: Wed, 01 Nov 2017 19:12:23 -0700 [thread overview]
Message-ID: <1509588743.31043.71.camel@perches.com> (raw)
As I was not there, and I know about as much as anyone
about printk internals, can you please post a recap of
what was discussed, technical and other, about printk
improvements at the kernel-summit?
If there was a pdf/powerpoint, that'd be nice to post too.
Thanks and cheers, Joe
next reply other threads:[~2017-11-02 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 2:12 Joe Perches [this message]
2017-11-02 12:45 ` printk discussions at KS 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=1509588743.31043.71.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=srostedt@redhat.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