From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Draft Agenda v2 for Kernel Summit
Date: Sat, 21 Oct 2017 06:53:02 -0400 [thread overview]
Message-ID: <20171021105302.arm4w3wn24o5b5x5@thunk.org> (raw)
The following is the v2 draft of the agenda for the Kernel Summit.
We will also have a track to allow for sessions that to be scheduled
"unconference style".
Please take a look and if you have any requests to reschedule any
sessions, please let me know.
- Ted
Tuesday
========
9:00 Keynotes
10:25 Coffee Break
10:55 Pulling away from the tracing ABI quicksand (Mattieu Desnoyers, Steve Rostedt)
11:45 Printk redesign (Petr Mladek & Steve Rostedt)
12:25 Lunch
14:05 Kernel Documentation (Mauro Carvalho)
14:55 Power Management (Rafael J. Wysocki)
15:35 Coffee Break
16:05 Restartable Sequences (Mathieu Desnoyers)
16:55 TBD
Onsite Attendee reception 5:35pm
Wednesday
=========
9:00 Keynotes
10:15 Conversation with Linus
10:35 Coffee break
11:05 Improve regression tracking (Thorsten Leemuis)
11:55 Kselftest use-cases (Shuah Khan)
12:35 lunch
14:15 Kernel Security (James Morris)
15:05 Kernel developer security hygiene (Konstantin Ryabitsev)
15:45 Coffee break
16:15 TBD
17:05 TAB Elections
All-Attendee reception 6pm
Tech topics that were discussed, but it's not clear whether we have
focus / someone to organize:
* Mobile phones
* Improving Kconfig
* Any of the more technical topics that were proposed for
maintainer summit, or if people want to do some pre-discussion
beforehand
next reply other threads:[~2017-10-21 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 10:53 Theodore Ts'o [this message]
2017-10-23 8:03 ` Mark Brown
[not found] ` <20171021134143.6e4d2f73@lwn.net>
2017-10-23 10:10 ` Theodore Ts'o
2017-10-23 11:27 ` Mathieu Desnoyers
2017-10-23 11:58 ` 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=20171021105302.arm4w3wn24o5b5x5@thunk.org \
--to=tytso@mit.edu \
--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