From: Jason Cooper <jason@lakedaemon.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] Kernel Summit Agenda -- 2nd draft
Date: Tue, 20 Oct 2015 23:17:35 +0000 [thread overview]
Message-ID: <20151020231735.GG3953@io.lakedaemon.net> (raw)
In-Reply-To: <20151020220328.GA21941@thunk.org>
Ted, all,
On Tue, Oct 20, 2015 at 06:03:28PM -0400, Theodore Ts'o wrote:
...
> Attendee list: https://sites.google.com/site/ksummit2015/attendee-list
Unfortunately, I will not be able to attend. I had a late schedule
change (well, a month out). I de-registered and emailed the relevant
people offlist at the time. I hope someone was able to take my slot...
> Tech topics
> ===========
>
> 1. Mainline kernel on a cellphone (Rob Herring)
> 2. Semantics of MMIO mapping attributes across archs (Benjamin Herrenschmidt)
> 3. System-wide interface to specify the level of PM tuning (Rafael J. Wysocki)
> 4. Giving freezer well-defined semantics (Jiri Kosina)
> 5. TBD
> 6. Benchmarking And Performance Trends (Chris Mason)
> 7. Mainlining PREEMPT_RT (Steven Rostedt)
> 8. Improving Kernel Security (James Morris / Kees Cook)
> 9. Developer Workflow Security (Panel)
Which means, I won't be able to participate in my own proposed topic. :(
Please let me know how it goes. Whoever is taking lead on this, please
get in touch with me if you have any questions about what I was
thinking.
> 10. Firmware signing (David Howells)
>
> 11. TBD
> 12. The Next Generation of the Media Controller (Mauro Carvalho Chehab)
> 13. Kernel support for compute-offload devices (Joerg Roedel)
> 14. TBD
> 15. IRQ affinity (Christoph Hellwig)
> 16. TBD
> 17. ZONE_DEVICE and Persistent Memory (Dan Williams)
> 18. TBD
> 19. TBD
> 20. Context tracking / nohz / RCU state (Andy Lutomirski / Paul McKenney)
>
> Core Day (Oct. 28th)
> ====================
>
> 9:00 - Welcome and agenda bashing
> 9:30 - Testing (Masahami, Shuah)
> 10:00 - Kernel Security - Readout and further discussion
I think this is the output of "Developer Workflow Security" as well as
"Improving Kernel Security".
thx,
Jason.
next prev parent reply other threads:[~2015-10-20 23:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:03 Theodore Ts'o
2015-10-20 23:17 ` Jason Cooper [this message]
2015-10-21 2:36 ` Olof Johansson
2015-10-21 14:56 ` Theodore Ts'o
2015-10-21 15:20 ` Guenter Roeck
2015-10-21 16:09 ` Mark Brown
2015-10-21 16:37 ` Guenter Roeck
2015-10-21 17:24 ` Luck, Tony
2015-10-21 18:53 ` Jonathan Corbet
2015-10-21 17:25 ` Mark Brown
2015-10-22 15:25 ` Theodore Ts'o
2015-10-22 20:01 ` Alexandre Belloni
2015-10-24 15:19 ` Rafael J. Wysocki
2015-10-26 5:56 ` Luis R. Rodriguez
2015-10-26 6:12 ` Eric W. Biederman
2015-10-26 6:28 ` Josh Triplett
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=20151020231735.GG3953@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=tytso@mit.edu \
/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