From: Mimi Zohar <zohar@linux.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Nayna Jain <nayna@linux.ibm.com>
Cc: James Morris <jmorris@namei.org>,
Matthew Garrett <mjg59@google.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: LSS-EU BoF(s) (renamed from LPC 2018)
Date: Tue, 23 Oct 2018 09:36:56 -0400 [thread overview]
Message-ID: <1540301816.5583.187.camel@linux.ibm.com> (raw)
In-Reply-To: <1540301465.2787.4.camel@HansenPartnership.com>
On Tue, 2018-10-23 at 14:31 +0100, James Bottomley wrote:
> On Tue, 2018-10-23 at 16:16 +0300, Jarkko Sakkinen wrote:
> > How can I join given that I have only ticket to LSS not to the
> > summit?
>
> According to Angela, the badges aren't a problem (they'll let you in)
> and I can have the the conference staff get us a room up to about 9pm
> tomorrow (although we'll have to start after the regular sessions end
> at 6pm).
>
> However, we need to pick a time so they can allocate us the room.
Ok, let's try and define an agenda of what needs to be discussed. The
original discussion started out by Chuck wanting to get together and
discuss IMA on distributed filesystems at LPC, and Monty chiming in
about IMA format.
It seems the discussion has diverged and is now about having a TPM BoF
the evening before LSS-EU, for those not staying for LSS. Let's try
and put together an agenda. Do we need/want another BoF for IMA?
Should that be Thurs evening?
Mimi
next prev parent reply other threads:[~2018-10-23 13:37 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
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 ` Mimi Zohar [this message]
2018-10-24 14:42 ` LSS-EU BoF(s) (renamed from LPC 2018) 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=1540301816.5583.187.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=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=nayna@linux.ibm.com \
--cc=serge@hallyn.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).