From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Quigley, David" <david.quigley@intel.com>,
Dan Middleton <dan.middleton@linux.intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: Re: No CCC Kernel SIG / device security meeting 9/27
Date: Fri, 27 Sep 2024 12:02:12 -0400 [thread overview]
Message-ID: <4065661639dd917f3410e51c23a65e4bb88fdaf3.camel@HansenPartnership.com> (raw)
In-Reply-To: <LV3PR11MB84582F1DDE696387B6272874E56B2@LV3PR11MB8458.namprd11.prod.outlook.com>
On Fri, 2024-09-27 at 15:52 +0000, Quigley, David wrote:
> Are there any recordings or some sort of record of what was discussed
> at the miniconf?
The broken out recordings should be uploaded within the next few weeks.
However, you can still use the livestream recording:
https://www.youtube.com/live/8XQwzUZxLK4
But it's monolithic, so you'll need to know time offsets of what you're
looking for.
Regards,
James
next prev parent reply other threads:[~2024-09-27 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 20:49 No CCC Kernel SIG / device security meeting 9/27 Dan Middleton
2024-09-27 15:52 ` Quigley, David
2024-09-27 16:02 ` James Bottomley [this message]
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=4065661639dd917f3410e51c23a65e4bb88fdaf3.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dan.middleton@linux.intel.com \
--cc=david.quigley@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).