ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Peter Huewe" <PeterHuewe@gmx.de>
To: "Peter Huewe" <PeterHuewe@gmx.de>
Cc: keyrings@linux-nfs.org,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	LSM List <linux-security-module@vger.kernel.org>,
	tpmdd-devel@lists.sourceforge.net,
	linux-ima-devel@lists.sourceforge.net,
	trousers-tech@lists.sourceforge.net
Subject: Re: [Ksummit-discuss] [tpmdd-devel] TPM MiniSummit @ LinuxCon Europe
Date: Mon, 13 Oct 2014 07:17:14 +0200	[thread overview]
Message-ID: <trinity-e8ea1a4b-495f-454d-ab9e-c4bc6d3097a7-1413177433975@3capp-gmx-bs14> (raw)
In-Reply-To: <trinity-a39c399d-cb0d-4c21-9832-85c3e26ba984-1413148618336@3capp-gmx-bs11>

Hi,
we got an official slot at Monday 5.30pm in Room 01 (http://sched.co/1D5VKBL) :)

Peter


Gesendet: Sonntag, 12. Oktober 2014 um 23:16 Uhr
Von: "Peter Huewe" <PeterHuewe@gmx.de>
An: "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com>
Cc: keyrings@linux-nfs.org, jarkko.sakkinnen@linux.intel.com, "ksummit-discuss@lists.linuxfoundation.org" <ksummit-discuss@lists.linuxfoundation.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, , "LSM List" <linux-security-module@vger.kernel.org>, tpmdd-devel@lists.sourceforge.net,, linux-ima-devel@lists.sourceforge.net, trousers-tech@lists.sourceforge.net
Betreff: Re: [tpmdd-devel] [Ksummit-discuss] TPM MiniSummit @ LinuxCon Europe
Hi
> apologies for top-posting but which day/time/place is this going to be held?
I'd suggest that we either meet tomorrow (Monday) during the other BoF Sessions @ 5:30pm or afterwards.
Does one of the attendees have a conflict with the BOFs or the VIP Reception?
Personally, I think it's most important that you Jarkko can join the meetup since you're developing the most on TPM2.0.


Since I don't have a special room booked, I'd suggest that we meet in the "Lobby" and then head out for a beer - since I haven't prepared any slides I would organize the meeting as a BOF.

Thanks,
Peter

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel[https://lists.sourceforge.net/lists/listinfo/tpmdd-devel]

      reply	other threads:[~2014-10-13  5:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  9:01 [Ksummit-discuss] " Peter Huewe
2014-09-23 16:42 ` Andy Lutomirski
2014-10-07 17:54   ` [Ksummit-discuss] [TrouSerS-tech] " Stefan Berger
2014-10-07 17:58     ` Andy Lutomirski
2014-10-07 18:02     ` [Ksummit-discuss] [tpmdd-devel] " Jason Gunthorpe
2014-10-07 18:47       ` Stefan Berger
2014-10-07 18:59         ` Andy Lutomirski
2014-10-13  0:03           ` Mimi Zohar
2014-10-08 20:59         ` Josh Triplett
2014-10-07 19:22     ` [Ksummit-discuss] " Jarkko Sakkinen
2014-10-12 23:45       ` [Ksummit-discuss] [tpmdd-devel] " Mimi Zohar
2014-10-12 18:17   ` [Ksummit-discuss] [tpmdd-devel] " Jarkko Sakkinen
2014-10-12 21:16     ` Peter Huewe
2014-10-13  5:17       ` Peter Huewe [this message]

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=trinity-e8ea1a4b-495f-454d-ab9e-c4bc6d3097a7-1413177433975@3capp-gmx-bs14 \
    --to=peterhuewe@gmx.de \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=keyrings@linux-nfs.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-ima-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=trousers-tech@lists.sourceforge.net \
    /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