From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
Jose Rivera <German.Rivera@freescale.com>
Subject: Re: location for new bus driver-- drivers/bus? drivers/misc?
Date: Tue, 12 Aug 2014 02:37:20 +0800 [thread overview]
Message-ID: <20140811183720.GC32566@kroah.com> (raw)
In-Reply-To: <9953b08b77224e738a1a1672dcf209c5@BY2PR0301MB0743.namprd03.prod.outlook.com>
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
next prev parent reply other threads:[~2014-08-11 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 16:25 location for new bus driver-- drivers/bus? drivers/misc? Stuart Yoder
2014-08-11 18:37 ` gregkh [this message]
2014-08-15 20:05 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140811183720.GC32566@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox