From: Mimi Zohar <zohar@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-integrity@vger.kernel.org
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Jerry Snitselaar" <jsnitsel@redhat.com>,
"Piotr Król" <piotr.krol@3mdeb.com>
Subject: Re: LPC System Boot and Security Microconference (subject change)
Date: Mon, 16 Sep 2019 08:06:53 -0400 [thread overview]
Message-ID: <1568635613.4975.40.camel@linux.ibm.com> (raw)
In-Reply-To: <20190916074657.GA26795@linux.intel.com>
On Mon, 2019-09-16 at 10:46 +0300, Jarkko Sakkinen wrote:
> My excuse is the overnight flight last night (no sleep).
Sorry I couldn't make LPC. Did anyone takes notes of the LPC System
Boot and Security microconference?
thanks,
Mimi
next prev parent reply other threads:[~2019-09-16 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 7:35 [PATCH] tpm: Fix tpm_send() length calculation Jarkko Sakkinen
2019-09-16 7:46 ` Jarkko Sakkinen
2019-09-16 12:06 ` Mimi Zohar [this message]
2019-09-16 13:44 ` LPC System Boot and Security Microconference (subject change) Jerry Snitselaar
2019-09-16 16:02 ` Piotr Król
2019-09-16 9:52 ` [PATCH] tpm: Fix tpm_send() length calculation kbuild test robot
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=1568635613.4975.40.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=piotr.krol@3mdeb.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).