netdev - Re: [PATCH net-next v15 0/5] PRU-ICSSM Ethernet Driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250905183151.6a0d832a@kernel.org>
Date: Fri, 5 Sep 2025 18:31:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Parvathi Pudi <parvathi@...thit.com>
Cc: danishanwar@...com, rogerq@...nel.org, andrew+netdev@...n.ch,
 davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
 robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 ssantosh@...nel.org, richardcochran@...il.com, m-malladi@...com,
 s.hauer@...gutronix.de, afd@...com, michal.swiatkowski@...ux.intel.com,
 jacob.e.keller@...el.com, horms@...nel.org, johan@...nel.org,
 alok.a.tiwari@...cle.com, m-karicheri2@...com, s-anna@...com,
 glaroque@...libre.com, saikrishnag@...vell.com, kory.maincent@...tlin.com,
 diogo.ivo@...mens.com, javier.carrasco.cruz@...il.com,
 basharath@...thit.com, linux-arm-kernel@...ts.infradead.org,
 netdev@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, vadim.fedorenko@...ux.dev,
 bastien.curutchet@...tlin.com, pratheesh@...com, prajith@...com,
 vigneshr@...com, praneeth@...com, srk@...com, rogerq@...com,
 krishna@...thit.com, pmohan@...thit.com, mohan@...thit.com
Subject: Re: [PATCH net-next v15 0/5] PRU-ICSSM Ethernet Driver

On Thu,  4 Sep 2025 15:45:37 +0530 Parvathi Pudi wrote:
> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS)
> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older
> Megabit ICSS (ICSSM).

Looks like the new code is not covered by the existing MAINTAINERS
entries. Who is expected to be maintaining the new driver?
Please consult:
https://docs.kernel.org/next/maintainer/feature-and-driver-maintainers.html