From: Alexey Kardashevskiy <aik@amd.com>
To: "Quigley, David" <david.quigley@intel.com>,
Xu Yilun <yilun.xu@linux.intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
ankita@nvidia.com, aneesh.kumar@kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-coco@lists.linux.dev
Subject: Re: [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP)
Date: Wed, 7 Oct 2026 23:21:44 +1100 [thread overview]
Message-ID: <95028cfa-9974-4e65-995a-6cfc627210e6@amd.com> (raw)
In-Reply-To: <cd7a7dd5-1aba-4986-8430-ca535fb34f22@amd.com>
On 15/9/26 12:07, Alexey Kardashevskiy wrote:
>
>
> On 15/9/26 05:29, Quigley, David wrote:
>> [You don't often get email from david.quigley@intel.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>>
>> Was there a decision made for a new meeting time? If not are we still
>> going to be meeting this week at Dan's original meeting time?
>
> No new decision is made yet.
>
> I dislike the idea of 2 separate calls, unlikely that both times are outside of my 00:00-06:00 so I am going to miss one of them constantly.
>
> Here we voted: https://crab.fit/iommufd-tsm-call-593432
For those who lost the link - here is a friendly reminder to vote. Thanks,
>
> 7/7 - no overlap. 6/7 - there are 2 options, 1hr each but I'll need Lu Baolu or Xu Yilun to cooperate :)
>
> So this friday call is likely to happen at the same old time. Thanks,
--
Alexey
next prev parent reply other threads:[~2026-10-07 13:21 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 22:08 [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Dan Williams
2026-07-05 22:08 ` [PATCH 01/15] netlink: specs: Introduce multi-message blobs for SPDM Dan Williams
2026-07-08 11:13 ` Donald Hunter
2026-07-11 1:43 ` Dan Williams (nvidia)
2026-07-08 13:23 ` Donald Hunter
2026-07-22 1:20 ` Jakub Kicinski
2026-08-02 17:58 ` Ankit Agrawal
2026-08-03 16:35 ` Jakub Kicinski
2026-07-05 22:08 ` [PATCH 02/15] tools: ynl: Teach pyynl to handle blobs Dan Williams
2026-07-08 13:48 ` Donald Hunter
2026-07-05 22:08 ` [PATCH 03/15] tools: ynl: Teach ynl_gen_c to validate and dump 'blob' attributes Dan Williams
2026-07-05 22:08 ` [PATCH 04/15] device core: Introduce "device evidence" over netlink Dan Williams
2026-07-08 13:22 ` Donald Hunter
2026-07-05 22:08 ` [PATCH 05/15] device core: Add "device evidence" 'validate' command Dan Williams
2026-07-05 22:08 ` [PATCH 06/15] PCI/TSM: Add device evidence support Dan Williams
2026-07-08 5:00 ` Alexey Kardashevskiy
2026-07-08 18:25 ` Dan Williams (nvidia)
2026-07-05 22:08 ` [PATCH 07/15] modules: Document the global async_probe parameter Dan Williams
2026-07-17 13:44 ` Nikolay Borisov
2026-07-05 22:08 ` [PATCH 08/15] device core: Initial device trust infrastructure Dan Williams
2026-07-06 13:45 ` Jason Gunthorpe
2026-07-05 22:08 ` [PATCH 09/15] PCI, device core: Move "untrusted" concept to DEVICE_TRUST_ADVERSARY Dan Williams
2026-07-06 13:49 ` Jason Gunthorpe
2026-07-07 13:04 ` Robin Murphy
2026-07-05 22:08 ` [PATCH 10/15] PCI/TSM: Add device interface security LOCKED support Dan Williams
2026-07-05 22:08 ` [PATCH 11/15] PCI/TSM: Add device interface security RUN support Dan Williams
2026-07-05 22:08 ` [PATCH 12/15] PCI/TSM: Add device interface security DMA enable/disable Dan Williams
2026-07-05 22:08 ` [PATCH 13/15] PCI, device core: Add private memory access for DEVICE_TRUST_TCB Dan Williams
2026-07-06 12:42 ` Aneesh Kumar K.V
2026-07-08 18:06 ` Dan Williams (nvidia)
2026-07-08 18:10 ` Aneesh Kumar K.V
2026-07-09 6:32 ` Alexey Kardashevskiy
2026-07-09 7:38 ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 14/15] PCI/TSM: Create MMIO descriptors via TDISP Report Dan Williams
2026-07-08 9:49 ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 15/15] PCI/TSM: Add relative MMIO offset support? Dan Williams
2026-07-08 2:25 ` Alexey Kardashevskiy
2026-07-08 18:05 ` Dan Williams (nvidia)
2026-07-06 12:51 ` [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Jason Gunthorpe
2026-07-06 20:55 ` Dan Williams (nvidia)
2026-07-07 12:43 ` Jason Gunthorpe
2026-07-08 0:12 ` Dan Williams (nvidia)
2026-07-08 14:31 ` Jason Gunthorpe
2026-07-09 2:45 ` Dan Williams (nvidia)
2026-07-09 13:36 ` Jason Gunthorpe
2026-07-15 9:04 ` Alexey Kardashevskiy
2026-07-16 18:51 ` Jason Gunthorpe
2026-07-28 8:20 ` Alexey Kardashevskiy
2026-07-28 23:29 ` Jason Gunthorpe
2026-08-04 1:48 ` Xu Yilun
2026-08-04 20:33 ` Ankit Agrawal
2026-08-05 17:43 ` Xu Yilun
2026-08-05 0:55 ` Jason Gunthorpe
2026-09-02 2:12 ` Xu Yilun
2026-09-02 2:20 ` Alexey Kardashevskiy
2026-09-02 7:28 ` Leon Romanovsky
2026-09-02 9:30 ` Xu Yilun
2026-09-02 15:01 ` Jason Gunthorpe
2026-09-03 2:21 ` Alexey Kardashevskiy
2026-09-03 5:59 ` Aneesh Kumar K.V
2026-09-03 6:51 ` Leon Romanovsky
2026-09-03 8:11 ` Ankit Agrawal
2026-09-03 11:04 ` Ankit Agrawal
2026-09-03 13:36 ` Lukas Wunner
2026-09-03 15:05 ` Dave Hansen
2026-09-03 17:53 ` Jason Gunthorpe
2026-09-03 20:02 ` Jonathan Cameron
2026-09-04 9:52 ` Jiri Pirko
2026-09-30 11:22 ` Jiri Pirko
2026-09-30 14:14 ` Quigley, David
2026-09-30 14:47 ` Jiri Pirko
2026-09-14 19:29 ` Quigley, David
2026-09-15 2:07 ` Alexey Kardashevskiy
2026-10-07 12:21 ` Alexey Kardashevskiy [this message]
2026-07-29 1:57 ` Ankit Agrawal
2026-08-02 18:12 ` Ankit Agrawal
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=95028cfa-9974-4e65-995a-6cfc627210e6@amd.com \
--to=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=ankita@nvidia.com \
--cc=david.quigley@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-coco@lists.linux.dev \
--cc=yilun.xu@linux.intel.com \
/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