On Wed, Mar 19, 2025 at 06:48:48AM +0100, Przemek Kitszel wrote: > On 3/18/25 17:06, Greg Kroah-Hartman wrote: > > 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 > > > > "platfrom" would also suggest a wider thing, so: > "complex"? > > anyway, I don't like fwctl, so maybe "fwctl" to at least reveal the real > reason :P 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/ FWCTL is unrelated to this discussion and you are not forced to use it if you don't like it. Thanks
