public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Stuart Yoder <stuart.yoder@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jose Rivera <German.Rivera@freescale.com>,
	Olof Johansson <olof@lixom.net>
Subject: Re: location for new bus driver-- drivers/bus? drivers/misc?
Date: Fri, 15 Aug 2014 22:05:18 +0200	[thread overview]
Message-ID: <201408152205.18871.arnd@arndb.de> (raw)
In-Reply-To: <20140811183720.GC32566@kroah.com>

On Monday 11 August 2014, gregkh@linuxfoundation.org wrote:
> 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?

I think it would be good to have this new driver in drivers/bus.

So far, I think all code in there has been merged through the
arm-soc tree, mainly because there is no other maintainer for it
yet. The drivers we have in there are not all the same kind,
the commonality ends at the point of being something that can
be considered a bus (so it fits here better than into MFD or misc)
and not being large enough to justify its own top-level directory.

I initially suggested actually moving some of the existing top-level
directories with simple bus drivers here too, but that was a bit
controversial, so I never followed up on that.

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

Sounds good, I'd be glad to have you listed as the official maintainer
so we can hand it off from the inofficial arm-soc adoption, and if it's
listed as part of the char/misc section, I will also be listed by
scripts/get_maintainer.pl to do reviews.

	Arnd

      reply	other threads:[~2014-08-15 20:05 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
2014-08-15 20:05   ` Arnd Bergmann [this message]

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=201408152205.18871.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=German.Rivera@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --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