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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250319112232.GJ1322339@unreal>
Date: Wed, 19 Mar 2025 13:22:32 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Przemek Kitszel <przemyslaw.kitszel@...el.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jason Gunthorpe <jgg@...dia.com>, Dave Jiang <dave.jiang@...el.com>,
	"Keller, Jacob E" <jacob.e.keller@...el.com>,
	David Ahern <dsahern@...nel.org>,
	"Nelson, Shannon" <shannon.nelson@....com>,
	Jiri Pirko <jiri@...nulli.us>, Jakub Kicinski <kuba@...nel.org>,
	Andy Gospodarek <andrew.gospodarek@...adcom.com>,
	Aron Silverton <aron.silverton@...cle.com>,
	"Williams, Dan J" <dan.j.williams@...el.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Christoph Hellwig <hch@...radead.org>,
	Itay Avraham <itayavr@...dia.com>, Jiri Pirko <jiri@...dia.com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Leonid Bloch <lbloch@...dia.com>,
	"linux-cxl@...r.kernel.org" <linux-cxl@...r.kernel.org>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Saeed Mahameed <saeedm@...dia.com>,
	"Sinyuk, Konstantin" <konstantin.sinyuk@...el.com>
Subject: Re: [PATCH v5 0/8] Introduce fwctl subystem

On Wed, Mar 19, 2025 at 11:46:15AM +0100, Przemek Kitszel wrote:
> 
> > We are discussing where to move XXX_core drivers which historically were
> > located in drivers/net/ethernet/XXX/, see this idea https://lore.kernel.org/all/20250211075553.GF17863@unreal/
> 
> yes, I know
> 
> > FWCTL is unrelated to this discussion and
> 
> it is related,
> I see the move as a workaround for "netdev maintainer complains more
> than I would like", sorry :P

No, it is not. There is no technical reason to keep non-netdev code in
netdev subsystem. If you have an explanation why PCI-to-AUX, VDPA, VFIO
and RDMA logic MUST be under netdev subsystem, please speak it now.

Otherwise please keep brigading out of this discussion.

Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ