Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Lukas Wunner <lukas@wunner.de>,
	Alexey Kardashevskiy <aik@amd.com>,
	Xu Yilun <yilun.xu@linux.intel.com>,
	ankita@nvidia.com, linux-coco@lists.linux.dev,
	linux-pci@vger.kernel.org, driver-core@lists.linux.dev,
	Aaron Tomlin <atomlin@atomlin.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Daniel Gomez <da.gomez@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Dexuan Cui <decui@microsoft.com>,
	Donald Hunter <donald.hunter@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Samuel Ortiz <sameo@rivosinc.com>,
	Saravana Kannan <saravanak@google.com>,
	Will Deacon <will@kernel.org>,
	"Fontenot, Nathan" <Nathan.Fontenot@amd.com>,
	rick.p.edgecombe@intel.com, yilun.xu@intel.com,
	Jiri Pirko <jiri@resnulli.us>, Leon Romanovsky <leon@kernel.org>,
	jonathan.cameron@oss.qualcomm.com
Subject: Re: [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP)
Date: Thu, 3 Sep 2026 21:02:23 +0100	[thread overview]
Message-ID: <20260903210223.43ec3e03@jic23-huawei> (raw)
In-Reply-To: <20260903175332.GN2890729@ziepe.ca>

On Thu, 3 Sep 2026 14:53:32 -0300
Jason Gunthorpe <jgg@ziepe.ca> wrote:

> On Thu, Sep 03, 2026 at 03:36:54PM +0200, Lukas Wunner wrote:
> > Dan was added as third devsec maintainer to host tsm.git:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/
> > 
> > Jonathan and I retain access to both repositories.  
> 
> Fortunately they are on kernel.org so Konstantin can always recover
> anything, we can get to that when there is a community consensus on
> the new team.
> 
> In the short term Linus doesn't care so much about where the tree
> comes from. Personally I'd rather leave that as is until the new team
> is ready to put work into it. It looks like there a number of things
> that may need preservation..
> 
> > > This is the only time Europe could reasonably participate in,
> > > obviously it is not OK for China and Aus.  
> > 
> > FWIW, I'm likewise based in Europe, as is Jonathan.  
> 
> I was wondering if we should try to have two calls on opposite
> sides.

I've shifted, now West Coast US.  However, given many things going
on at the moment, my direct involvement in this may be limited for now.

I'll be pulling in some other Qualcomm folk though to help out where
we can. Most like mixture of US and India based folk.

> 
> > Obviously, one cannot separate discussing Dan's work from Dan.  
> 
> Yes, please lets all have patience and understanding
> 
> Personally I feel seeing the overall work finished and products using
> it in the market will be a "in memorandum" dedication for Dan.

Fully agree with this sentiment as one of the ways to remember Dan.

Jonathan

> 
> Jason


  reply	other threads:[~2026-09-03 20:02 UTC|newest]

Thread overview: 70+ 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 [this message]
2026-09-04  9:52                 ` Jiri Pirko
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=20260903210223.43ec3e03@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Nathan.Fontenot@amd.com \
    --cc=aik@amd.com \
    --cc=alistair.francis@wdc.com \
    --cc=aneesh.kumar@kernel.org \
    --cc=ankita@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=atomlin@atomlin.com \
    --cc=bhelgaas@google.com \
    --cc=da.gomez@kernel.org \
    --cc=dakr@kernel.org \
    --cc=decui@microsoft.com \
    --cc=donald.hunter@gmail.com \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgg@ziepe.ca \
    --cc=jiri@resnulli.us \
    --cc=jonathan.cameron@oss.qualcomm.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mcgrof@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=rafael@kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=robin.murphy@arm.com \
    --cc=sameo@rivosinc.com \
    --cc=samitolvanen@google.com \
    --cc=saravanak@google.com \
    --cc=will@kernel.org \
    --cc=yilun.xu@intel.com \
    --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