From: Dan Middleton <dan.middleton@linux.intel.com>
To: linux-coco@lists.linux.dev
Subject: Confidential Computing call May 10: RTMR ABI & TEE I/O
Date: Fri, 3 May 2024 14:55:20 -0500 [thread overview]
Message-ID: <61b65115-5945-4e27-89e4-bb6cba657f7f@linux.intel.com> (raw)
Hi
Next Friday, May 10th at 9am PDT, we have a Confidential Computing
devsec / BoF / Discussion Group / SIG call. Everyone is welcome.
Tentative agenda includes RTMR ABI v3 direction and TEE I/O next steps.
We may still have some logistical kinks but hopefully this is pretty
accessible. We are alternating times every other week that we hope
will accommodate contributors across different time zones.
The call is hosted by the Linux Foundation / Confidential Computing
Consortium.
Zoom and other logistics at the link:
https://confidentialcomputing.io/about/committees/#Linux-Kernel-SIG
The next several meetings are
May 10th Friday at 9am Pacific Time
May 23rd Thursday at 8pm Pacific Time
June 7th Friday at 9am Pacific Time
June 20th Thursday at 8pm Pacific Time
Regards,
Dan Middleton
next reply other threads:[~2024-05-03 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:55 Dan Middleton [this message]
2024-05-07 16:17 ` Confidential Computing call May 10: RTMR ABI & TEE I/O James Bottomley
2024-05-13 5:10 ` Samuel Ortiz
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=61b65115-5945-4e27-89e4-bb6cba657f7f@linux.intel.com \
--to=dan.middleton@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
/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).