From: Kees Cook <keescook@chromium.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] DRAFT Kernel Summit Track schedule
Date: Thu, 29 Aug 2019 22:53:54 -0700 [thread overview]
Message-ID: <201908292248.12974C32@keescook> (raw)
In-Reply-To: <20190830035117.GB5670@mit.edu>
On Thu, Aug 29, 2019 at 11:51:17PM -0400, Theodore Y. Ts'o wrote:
> On Wed, Aug 28, 2019 at 09:23:08PM +0200, Christian Brauner wrote:
> > On Mon, Aug 26, 2019 at 05:25:48PM -0400, Theodore Ts'o wrote:
> > > This is a draft kernel summit track schedule. Please let me know of
> > > any potential conflicts or schedule changes that you might like to
> > > make.
> >
> > Could we grab a slot for
> > https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2019-July/006699.html
> > please? It doesn't seem to appear in the list yet.
>
> I hadn't scheduled this because it seemed to be a fairly specialized
> topic, and one of the major contributors to the thread (Andy
> Lutomirski) won't be able to be there. Will we have the right people
> to have this discussion in Lisbon?
I agree it would be better to have Andy there, but I don't think that's
reason enough to not discuss it. We had a rather large BoF meeting at LSS
about it with a circle of maybe 15-20 people where we made some headway
on understanding some of the larger requirements, but there was a lot
left to discuss. I know several people from that discussion will be in
Lisbon, though I agree it's somewhat specialized. I'm not sure what the
"interest level" cut-off is for a ksummit slot, but I know I'll need to
spend time talking with a bunch of people about it in person while I'm
there, so at least having some "unscheduled" slots for similar kinds of
discussions would be value.
--
Kees Cook
next prev parent reply other threads:[~2019-08-30 5:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 21:25 [Ksummit-discuss] DRAFT Kernel Summit Track schedule Theodore Y. Ts'o
2019-08-28 19:23 ` Christian Brauner
2019-08-30 3:51 ` Theodore Y. Ts'o
2019-08-30 5:53 ` Kees Cook [this message]
2019-09-05 0:12 ` Theodore Y. Ts'o
2019-09-05 19:47 ` Kees Cook
2019-08-28 20:13 ` Dave Airlie
2019-08-30 3:49 ` Theodore Y. Ts'o
2019-09-01 8:09 ` Daniel Vetter
2019-08-28 20:29 ` Shuah Khan
2019-08-30 3:54 ` Theodore Y. 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=201908292248.12974C32@keescook \
--to=keescook@chromium.org \
--cc=christian.brauner@ubuntu.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 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.