From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev, linux-coco@lists.linux.dev
Subject: SVSM Development Call June 12th, 2024
Date: Wed, 12 Jun 2024 14:28:23 +0200 [thread overview]
Message-ID: <ZmmUZ5-DoVjKtoE3@8bytes.org> (raw)
Hi,
Here is the usual call for agenda items for this weeks SVSM development
call. Please send me any agenda items you have in mind or raise them in
the meeting.
For now we have these items from Claudio:
- What does TPM locality[1] mean for the SVSM vTPM?
- Is there any SVSM boot event that we want to record in the TPM
PCRs/Event log? E.g. a SVSM configuration, the OVMF hash, etc
Please note that there will be no SVSM Development Call next week, as I
will be at SUSECon on Wednesday. Next call after today will happen on
June 26th.
Details of the meeting (GMeet and Calendar links, meeting time) can be
found in our governance repository at:
https://github.com/coconut-svsm/governance
The meeting will be recorded and the recording eventually published.
See you all there.
Regards,
Jörg
next reply other threads:[~2024-06-12 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 12:28 Jörg Rödel [this message]
2024-06-13 7:41 ` [svsm-devel] SVSM Development Call June 12th, 2024 Jörg Rödel
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=ZmmUZ5-DoVjKtoE3@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-coco@lists.linux.dev \
--cc=svsm-devel@coconut-svsm.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 NNTP newsgroup(s).