From: Dan Middleton <dan.middleton@linux.intel.com>
To: linux-coco@lists.linux.dev
Subject: No CCC Kernel SIG / device security meeting 9/27
Date: Thu, 26 Sep 2024 15:49:28 -0500 [thread overview]
Message-ID: <7a2e450e-bc83-45f9-ae86-b1872ae0aa23@linux.intel.com> (raw)
No Device security / Confidential Computing Consortium Kernel SIG
meeting this week.
Those lucky enough to visit Vienna last week are still digesting LPC
conversations this week. :)
Regards,
Dan Middleton
next reply other threads:[~2024-09-26 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 20:49 Dan Middleton [this message]
2024-09-27 15:52 ` No CCC Kernel SIG / device security meeting 9/27 Quigley, David
2024-09-27 16:02 ` James Bottomley
2024-09-27 20:15 ` Quigley, David
2024-09-29 23:24 ` 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=7a2e450e-bc83-45f9-ae86-b1872ae0aa23@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 NNTP newsgroup(s).