From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mimi Zohar <zohar@linux.ibm.com>, James Morris <jmorris@namei.org>
Cc: Matthew Garrett <mjg59@google.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
montywiseman32@gmail.com, serge@hallyn.com,
chuck.lever@oracle.com,
linux-integrity <linux-integrity@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: LPC 2018
Date: Tue, 16 Oct 2018 12:13:07 -0700 [thread overview]
Message-ID: <1539717187.2805.62.camel@HansenPartnership.com> (raw)
In-Reply-To: <1539716981.11939.373.camel@linux.ibm.com>
On Tue, 2018-10-16 at 15:09 -0400, Mimi Zohar wrote:
> On Tue, 2018-10-16 at 08:34 -0700, James Bottomley wrote:
> > On Tue, 2018-10-16 at 07:56 -0400, Mimi Zohar wrote:
> > > On Tue, 2018-10-16 at 09:46 +1100, James Morris wrote:
> > > > On Mon, 15 Oct 2018, James Bottomley wrote:
> > > >
> > > > > > What about a TPM BoF at LSS
> > > > >
> > > > > I'm only at LinuxCon/KS, so I'm leaving on Thursday. I think
> > > > > you have a Wednesday overlap, though, so Wednesday would
> > > > > work.
> > > >
> > > > LSS is Thurs+Fri, but we may have a quorum for Weds.
> > >
> > > Some of us are arriving Wed. Perhaps try scheduling it later in
> > > the day Wed.
> >
> > Oh, I thought LSS was three days: Wed-Fri with the Wed talks being
> > open to all LinuxCon attendees ... I even made a note to go to some
> > of them. Did that get killed?
>
> We've considered expanding LSS to three days, but for the time being
> it is only two days.
Actually, I looked at what I was planning to go to and it was KVM Forum
that was doing the Wednesday overlap, not LSS ... I just had a security
part of that noted down as interesting which is why I was confused.
jaems
next prev parent reply other threads:[~2018-10-17 3:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 15:58 LPC 2018 Chuck Lever
2018-10-10 1:05 ` Monty Wiseman
2018-10-11 15:48 ` Serge E. Hallyn
2018-10-11 19:49 ` Monty Wiseman
2018-10-11 22:18 ` James Bottomley
2018-10-15 13:53 ` Jarkko Sakkinen
2018-10-15 18:48 ` Matthew Garrett
2018-10-15 21:35 ` James Morris
2018-10-15 22:28 ` James Bottomley
2018-10-15 22:46 ` James Morris
2018-10-16 11:56 ` Mimi Zohar
2018-10-16 11:56 ` Mimi Zohar
2018-10-16 15:34 ` James Bottomley
2018-10-16 19:09 ` Mimi Zohar
2018-10-16 19:13 ` James Bottomley [this message]
2018-10-18 0:05 ` Jarkko Sakkinen
2018-10-20 18:23 ` Nayna Jain
2018-10-23 13:16 ` Jarkko Sakkinen
2018-10-23 13:31 ` James Bottomley
2018-10-23 13:36 ` LSS-EU BoF(s) (renamed from LPC 2018) Mimi Zohar
2018-10-24 14:42 ` Monty Wiseman
2018-10-24 15:55 ` Aw: " Peter Huewe
2018-10-24 16:25 ` Mimi Zohar
2018-10-24 16:28 ` James Bottomley
2018-10-25 7:14 ` Jarkko Sakkinen
2018-10-23 13:39 ` LPC 2018 David Howells
2018-10-23 13:47 ` James Bottomley
2018-10-23 13:56 ` David Howells
2018-10-24 8:45 ` Jarkko Sakkinen
2018-10-24 8:59 ` James Bottomley
2018-10-24 9:17 ` Monty Wiseman
2018-10-24 15:27 ` Jarkko Sakkinen
2018-10-24 15:54 ` Roberto Sassu
2018-10-24 16:05 ` James Bottomley
2018-10-17 23:49 ` Jarkko Sakkinen
2018-10-17 23:47 ` Jarkko Sakkinen
2018-10-17 23:48 ` James Bottomley
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=1539717187.2805.62.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=montywiseman32@gmail.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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 NNTP newsgroup(s).