From: <dan.j.williams@intel.com>
To: <linux-coco@lists.linux.dev>
Cc: <david.quigley@intel.com>, <mathieu.poirier@linaro.org>
Subject: CCC TEE I/O Meeting Agenda for February 5th at 8pm (PST)
Date: Thu, 5 Feb 2026 15:19:33 -0800 [thread overview]
Message-ID: <6985258510555_68d31001e@dwillia2-mobl4.notmuch> (raw)
The meeting [1] is on for tonight. I have a late breaking conflict and
will need to leave early. Please respond to this message with topics for
opens. I have asked Dave Quigley to chair in my absence. We may not get
to the "IOMMU setup consensus" topic depending on the evidence
collection ABI discussion. The other topics are short.
Agenda:
- Opens
- PCI power management vs DOE power management vs TSM operations
- See pm_runtime_resume_and_get() usage [2]
- What's cooking for devsec-20260205?
- Next steps for device evidence collection ABI (Dave and Mathieu)
- IOMMU setup consensus (continued from Discord conversation [3])
[1]: Registration: https://zoom-lfx.platform.linuxfoundation.org/meeting/93219227394?password=80705486-101a-4e19-8f11-0baaf92104be&invite=true
[2]: https://github.com/l1k/linux/commit/f8343c60e130
[3]: https://discord.com/channels/1123803528377413762/1468465977376378910
reply other threads:[~2026-02-05 23:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6985258510555_68d31001e@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=david.quigley@intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=mathieu.poirier@linaro.org \
/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