From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Draft Agenda for the Kernel Summit
Date: Tue, 31 Oct 2017 12:16:32 -0600 [thread overview]
Message-ID: <20171031121632.2d7f87a4@lwn.net> (raw)
In-Reply-To: <1509426625.26592.41.camel@perches.com>
On Mon, 30 Oct 2017 22:10:25 -0700
Joe Perches <joe@perches.com> wrote:
> I would appreciate a recap of the printk discussions
I'll get there, hopefully soon.
jon
next prev parent reply other threads:[~2017-10-31 18:16 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 0:15 [Ksummit-discuss] Draft Agenda for the Kernel Summit Theodore Ts'o
2017-10-13 18:28 ` Konstantin Ryabitsev
2017-10-20 0:30 ` Theodore Ts'o
2017-10-16 6:35 ` James Morris
2017-10-19 11:35 ` Mauro Carvalho Chehab
2017-10-19 21:02 ` [Ksummit-discuss] Documentation session (was: Draft Agenda for the Kernel Summit) Jonathan Corbet
2017-10-20 0:32 ` [Ksummit-discuss] Draft Agenda for the Kernel Summit Theodore Ts'o
2017-10-23 12:49 ` [Ksummit-discuss] Documentation session (was: Draft Agenda for the Kernel Summit) Mauro Carvalho Chehab
2017-10-20 0:53 ` [Ksummit-discuss] Draft Agenda for the Kernel Summit Rafael J. Wysocki
2017-10-20 19:46 ` Theodore Ts'o
2017-10-21 1:02 ` Rafael J. Wysocki
2017-10-20 2:18 ` Theodore Ts'o
2017-10-20 3:32 ` Thorsten Leemhuis
2017-10-20 11:19 ` Rafael J. Wysocki
2017-10-20 2:19 ` Theodore Ts'o
2017-10-20 14:31 ` Shuah Khan
2017-10-20 15:27 ` James Bottomley
2017-10-20 19:16 ` Shuah Khan
2017-10-20 6:04 ` Steven Rostedt
2017-10-20 15:57 ` Joe Perches
2017-10-20 19:50 ` Theodore Ts'o
2017-10-31 5:10 ` Joe Perches
2017-10-31 18:16 ` Jonathan Corbet [this message]
[not found] <1445272350.2481.40.camel@loki>
2015-10-19 18:52 ` [Ksummit-discuss] Draft agenda for the kernel summit Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-10-12 19:01 Theodore Ts'o
2015-10-13 4:00 ` Josh Triplett
2015-10-13 13:31 ` Linus Walleij
2015-10-16 0:41 ` Rob Herring
2015-10-16 6:52 ` Johannes Berg
2015-10-16 7:55 ` Arnd Bergmann
2015-10-16 8:00 ` Marcel Holtmann
2015-10-16 8:37 ` Arnd Bergmann
2015-10-16 9:21 ` Linus Walleij
2015-10-16 8:00 ` Johannes Berg
2015-10-16 7:57 ` Samuel Ortiz
2015-10-16 8:45 ` Geert Uytterhoeven
2015-10-16 13:09 ` Rob Herring
2015-10-16 9:03 ` Mark Brown
2015-10-16 8:04 ` Christian Borntraeger
2015-10-19 12:33 ` Mauro Carvalho Chehab
2015-10-19 13:53 ` Mark Brown
2015-10-19 16:27 ` Liam Girdwood
2015-10-19 19:34 ` Mauro Carvalho Chehab
2015-10-19 20:46 ` Shuah Khan
2015-10-20 11:55 ` Liam Girdwood
2015-10-20 13:22 ` Mark Brown
2015-10-20 15:34 ` Mauro Carvalho Chehab
2015-10-22 8:34 ` Sakari Ailus
2015-10-22 8:49 ` Sakari Ailus
2015-10-20 15:18 ` Mauro Carvalho Chehab
2015-10-20 15:47 ` Takashi Iwai
2015-10-20 16:11 ` Mauro Carvalho Chehab
2015-10-20 23:39 ` Shuah Khan
2015-10-20 13:13 ` Mark Brown
2015-10-20 15:29 ` Mauro Carvalho Chehab
2015-10-20 15:56 ` Mark Brown
2015-10-21 0:04 ` Laurent Pinchart
2015-10-21 10:24 ` Liam Girdwood
2015-10-21 10:24 ` Mark Brown
2015-10-21 8:59 ` Geert Uytterhoeven
2015-10-19 18:48 ` Jonathan Cameron
2014-08-11 22:45 Theodore Ts'o
[not found] ` <alpine.DEB.2.10.1408152014100.2503@hadrien>
2014-08-15 22:35 ` Theodore Ts'o
2014-08-16 0:27 ` Darren Vincent Hart
2014-08-16 2:17 ` Theodore Ts'o
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=20171031121632.2d7f87a4@lwn.net \
--to=corbet@lwn.net \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).