From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel security
Date: Thu, 12 Oct 2017 14:21:12 +0300 [thread overview]
Message-ID: <20171012112112.tt3zbmfrealfqv56@linux.intel.com> (raw)
In-Reply-To: <20171009162325.ia2qtrej6w2vrcrb@linux.intel.com>
On Mon, Oct 09, 2017 at 07:23:25PM +0300, Jarkko Sakkinen wrote:
> On Thu, Sep 28, 2017 at 08:27:59PM +0300, Jarkko Sakkinen wrote:
> > On Sat, 2017-09-23 at 14:24 +1000, James Morris wrote:
> > > I'd like to propose a kernel security tech topic, where we can discuss
> > > current development issues, with both core kernel folk and European
> > > security developers who may not have attended LSS.
> > >
> > > Potential agenda items include:
> > >
> > > - KSPP update (Kees Cook)
> > > - TPM status (Jarkko, if available)
> > > - LSS & LPC container security discussion readout (myself)
> > >
> > > And possibly other items depending on who is available at the conference,
> > > and how much time is available for the topic
> >
> > I apologize for late response. I just sent a travel request and should get
> > response next week.
> >
> > /Jarkko
>
> My travel request was accepted. I will be available.
>
> /Jarkko
My flights have been booked. Is there a speaker code I should use when I
register?
/Jarkko
next prev parent reply other threads:[~2017-10-12 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 4:24 [Ksummit-discuss] [TECH TOPIC] Kernel security James Morris
2017-09-28 17:27 ` Jarkko Sakkinen
2017-10-09 16:23 ` Jarkko Sakkinen
2017-10-12 11:21 ` Jarkko Sakkinen [this message]
2017-09-28 22:50 ` James Morris
2017-09-28 23:09 ` Jason A. Donenfeld
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=20171012112112.tt3zbmfrealfqv56@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--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).