From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 1/2] drivers: misc: omap: add a new driver for ocp2scp
Date: Mon, 16 Jul 2012 19:47:01 +0000 [thread overview]
Message-ID: <201207161947.01751.arnd@arndb.de> (raw)
In-Reply-To: <CAAe_U6JMGP3jEkkd=vqpR5KTeOnY51AOcb65zqKRRa8MtnWjzQ@mail.gmail.com>
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.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "ABRAHAM, KISHON VIJAY" <kishon@ti.com>
Cc: 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, tony@atomide.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: Mon, 16 Jul 2012 19:47:01 +0000 [thread overview]
Message-ID: <201207161947.01751.arnd@arndb.de> (raw)
In-Reply-To: <CAAe_U6JMGP3jEkkd=vqpR5KTeOnY51AOcb65zqKRRa8MtnWjzQ@mail.gmail.com>
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.
Arnd
next prev parent reply other threads:[~2012-07-16 19:47 UTC|newest]
Thread overview: 27+ 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 ` Kishon Vijay Abraham I
2012-06-22 13:15 ` 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-22 13:15 ` Kishon Vijay Abraham I
2012-06-22 13:15 ` Kishon Vijay Abraham I
2012-06-23 4:44 ` Greg KH
2012-06-23 4:44 ` Greg KH
2012-06-25 5:39 ` ABRAHAM, KISHON VIJAY
2012-06-25 5:39 ` ABRAHAM, KISHON VIJAY
2012-06-25 12:24 ` Felipe Balbi
2012-06-25 12:24 ` Felipe Balbi
2012-06-25 16:26 ` Arnd Bergmann
2012-06-25 16:26 ` Arnd Bergmann
2012-07-16 8:12 ` Felipe Balbi
2012-07-16 8:12 ` Felipe Balbi
2012-07-16 8:12 ` Felipe Balbi
2012-07-16 8:28 ` ABRAHAM, KISHON VIJAY
2012-07-16 8:28 ` ABRAHAM, KISHON VIJAY
2012-07-16 8:28 ` ABRAHAM, KISHON VIJAY
2012-07-16 19:47 ` Arnd Bergmann [this message]
2012-07-16 19:47 ` Arnd Bergmann
2012-07-18 7:35 ` Tony Lindgren
2012-07-18 7:35 ` Tony Lindgren
2012-06-22 13:15 ` [RFC PATCH v2 2/2] arm/dts: omap4: Add ocp2scp data Kishon Vijay Abraham I
2012-06-22 13:15 ` Kishon Vijay Abraham I
2012-06-22 13:15 ` 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=201207161947.01751.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.