netdev - Re: [PATCH v5 0/8] Introduce fwctl subystem

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: <2025031836-monastery-imaginary-7f5e@gregkh>
Date: Tue, 18 Mar 2025 17:06:17 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Dave Jiang <dave.jiang@...el.com>
Cc: Jason Gunthorpe <jgg@...dia.com>,
	"Keller, Jacob E" <jacob.e.keller@...el.com>,
	David Ahern <dsahern@...nel.org>,
	"Nelson, Shannon" <shannon.nelson@....com>,
	Leon Romanovsky <leon@...nel.org>, 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 Tue, Mar 18, 2025 at 08:39:50AM -0700, Dave Jiang wrote:
> 
> 
> On 3/18/25 6:25 AM, Jason Gunthorpe wrote:
> > On Tue, Mar 18, 2025 at 02:20:45PM +0100, Greg Kroah-Hartman wrote:
> > 
> >> Yes, note, the issue came up in the 2.5.x kernel days, _WAY_ before we
> >> had git, so this wasn't a git issue.  I'm all for "drivers/core/" but
> >> note, that really looks like "the driver core" area of the kernel, so
> >> maybe pick a different name?
> > 
> > Yeah, +1. We have lots of places calling what is in drivers/base 'core'.
> 
> just throwing in my 2c
> 
> drivers/main

Implies the "driver core"

> drivers/common

lib/ maybe?

> drivers/primary

It's not going to be the primary drivers for my laptop :)

Naming is hard.  Let's see some code first...

greg k-h