devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "ABRAHAM, KISHON VIJAY" <kishon@ti.com>,
	balbi@ti.com, Greg KH <gregkh@linuxfoundation.org>,
	grant.likely@secretlab.ca, rob.herring@calxeda.com,
	rob@landley.net, linux@arm.linux.org.uk, b-cousson@ti.com,
	rnayak@ti.com, devicetree-discuss@lists.ozlabs.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v2 1/2] drivers: misc: omap: add a new driver for ocp2scp
Date: Wed, 18 Jul 2012 00:35:08 -0700	[thread overview]
Message-ID: <20120718073507.GL6522@atomide.com> (raw)
In-Reply-To: <201207161947.01751.arnd@arndb.de>

* Arnd Bergmann <arnd@arndb.de> [120716 12:51]:
> On Monday 16 July 2012, ABRAHAM, KISHON VIJAY wrote:
> > >>
> > >> I think we should reconsider the idea of drivers/bus/ with a file per
> > >> bus in there at least for new buses, but doing a new drivers/scp/
> > >> would be ok for me if there is enough opposition against the idea
> > >> of drivers/bus aggregating different buses.
> > >
> > > I don't mind either way. The fact is that this ocp-to-scp bridge is
> > > really a TI/OMAP thing. Not sure it deserves a directory of its own.
> > 
> > Ok. Then I'll have a file in drivers/bus/ for ocp2scp driver.
> 
> Sounds good to me. I don't care if it's the only file in that directory.
> We can point the next person to a bus with a single file to that directory
> and let them add theirs.

Yes great. Sounds like that's where the omap GPMC bus driver should
end up going eventually.

Regards,

Tony

  reply	other threads:[~2012-07-18  7:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 13:15 [RFC PATCH v2 0/2] omap: add ocp2scp as a misc driver Kishon Vijay Abraham I
2012-06-22 13:15 ` [RFC PATCH v2 1/2] drivers: misc: omap: add a new driver for ocp2scp Kishon Vijay Abraham I
2012-06-23  4:44   ` Greg KH
2012-06-25  5:39     ` ABRAHAM, KISHON VIJAY
2012-06-25 12:24       ` Felipe Balbi
2012-06-25 16:26         ` Arnd Bergmann
     [not found]           ` <201206251626.09666.arnd-r2nGTMty4D4@public.gmane.org>
2012-07-16  8:12             ` Felipe Balbi
     [not found]               ` <20120716081204.GI7955-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-07-16  8:28                 ` ABRAHAM, KISHON VIJAY
2012-07-16 19:47                   ` Arnd Bergmann
2012-07-18  7:35                     ` Tony Lindgren [this message]
     [not found] ` <1340370942-23201-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2012-06-22 13:15   ` [RFC PATCH v2 2/2] arm/dts: omap4: Add ocp2scp data Kishon Vijay Abraham I

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=20120718073507.GL6522@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rnayak@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    /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;
as well as URLs for NNTP newsgroup(s).