linux-kernel - Re: location for new bus driver-- drivers/bus? drivers/misc?

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]

Date:	Tue, 12 Aug 2014 02:37:20 +0800
From:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:	Stuart Yoder <stuart.yoder@...escale.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"arnd@...db.de" <arnd@...db.de>,
	Jose Rivera <German.Rivera@...escale.com>
Subject: Re: location for new bus driver-- drivers/bus? drivers/misc?

On Mon, Aug 11, 2014 at 04:25:49PM +0000, Stuart Yoder wrote:
> Greg,
> 
> We (Freescale) have a patch series nearly ready to send out
> for a new bus driver.  It's for a block we call the Freescale
> 'Management Complex' which manages discoverable hardware objects.
> The Linux bus driver enumerates these objects, binds discovered
> objects to drivers just like PCI or any normal bus driver.

Sounds good.

> Question is-- where should this go in the kernel and who would
> the maintainer be to cc: the RFC?  I don't think it warrants
> a top level driver directory beside pci, usb, etc.  Most likely
> place is drivers/bus or drivers/misc (?).
> 
> We currently have it in drivers/bus, but as far as I can see
> there is no maintainer per se for that directory.  You and 
> Arnd manage misc so thought I would ask.

I don't remember why drivers/bus/ came about, Arnd, you created it,
should we be putting random bus controllers in this directory?

And if so, sure, I can maintain drivers/bus/ along with the misc/char
drivers, it's not a big deal.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/