From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Roger Quadros <rogerq@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Vutla, Lokesh" <lokeshvutla@ti.com>,
"Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH 3/3] drivers: bus: Move omap gpmc code to live under drivers
Date: Fri, 21 Nov 2014 08:18:22 -0800 [thread overview]
Message-ID: <20141121161821.GS7046@atomide.com> (raw)
In-Reply-To: <3449576.YFhSXUYQOn@wuerfel>
* Arnd Bergmann <arnd@arndb.de> [141121 03:17]:
> On Friday 21 November 2014 11:15:05 Roger Quadros wrote:
> > On 11/21/2014 12:28 AM, Tony Lindgren wrote:
> > > Just move to drivers as further clean-up can now happen there
> > > finally.
>
> Awesome!
>
> > > arch/arm/mach-omap2/Kconfig | 1 +
> > > arch/arm/mach-omap2/Makefile | 2 +-
> > > drivers/bus/Kconfig | 3 +++
> > > drivers/bus/Makefile | 3 ++-
> > > arch/arm/mach-omap2/gpmc.c => drivers/bus/omap-gpmc.c | 0
> > > 5 files changed, 7 insertions(+), 2 deletions(-)
> > > rename arch/arm/mach-omap2/gpmc.c => drivers/bus/omap-gpmc.c (100%)
> >
> > Should we move it to drivers/memory/ instead?
> > TI_AEMIF driver lives there. This is similar to OMAP-GPMC for but for
> > Davinci and Keystone platforms.
>
> Agreed, using drivers/memory sounds better.
Good point, I forgot we have separate drivers/memory and drivers/bus.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] drivers: bus: Move omap gpmc code to live under drivers
Date: Fri, 21 Nov 2014 08:18:22 -0800 [thread overview]
Message-ID: <20141121161821.GS7046@atomide.com> (raw)
In-Reply-To: <3449576.YFhSXUYQOn@wuerfel>
* Arnd Bergmann <arnd@arndb.de> [141121 03:17]:
> On Friday 21 November 2014 11:15:05 Roger Quadros wrote:
> > On 11/21/2014 12:28 AM, Tony Lindgren wrote:
> > > Just move to drivers as further clean-up can now happen there
> > > finally.
>
> Awesome!
>
> > > arch/arm/mach-omap2/Kconfig | 1 +
> > > arch/arm/mach-omap2/Makefile | 2 +-
> > > drivers/bus/Kconfig | 3 +++
> > > drivers/bus/Makefile | 3 ++-
> > > arch/arm/mach-omap2/gpmc.c => drivers/bus/omap-gpmc.c | 0
> > > 5 files changed, 7 insertions(+), 2 deletions(-)
> > > rename arch/arm/mach-omap2/gpmc.c => drivers/bus/omap-gpmc.c (100%)
> >
> > Should we move it to drivers/memory/ instead?
> > TI_AEMIF driver lives there. This is similar to OMAP-GPMC for but for
> > Davinci and Keystone platforms.
>
> Agreed, using drivers/memory sounds better.
Good point, I forgot we have separate drivers/memory and drivers/bus.
Regards,
Tony
next prev parent reply other threads:[~2014-11-21 16:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 22:28 [PATCH 0/3] Move omap GPMC to live in drivers/bus Tony Lindgren
2014-11-20 22:28 ` Tony Lindgren
2014-11-20 22:28 ` [PATCH 1/3] ARM: OMAP2+: Prepare to move GPMC to drivers by platform data header Tony Lindgren
2014-11-20 22:28 ` Tony Lindgren
2014-11-21 9:28 ` Roger Quadros
2014-11-21 9:28 ` Roger Quadros
2014-11-21 16:15 ` Tony Lindgren
2014-11-21 16:15 ` Tony Lindgren
2014-11-21 16:55 ` Tony Lindgren
2014-11-21 16:55 ` Tony Lindgren
2014-11-20 22:28 ` [PATCH 2/3] ARM: OMAP2+: Move GPMC initcall to devices.c Tony Lindgren
2014-11-20 22:28 ` Tony Lindgren
2014-11-21 9:41 ` Roger Quadros
2014-11-21 9:41 ` Roger Quadros
2014-11-21 16:17 ` Tony Lindgren
2014-11-21 16:17 ` Tony Lindgren
2014-11-20 22:28 ` [PATCH 3/3] drivers: bus: Move omap gpmc code to live under drivers Tony Lindgren
2014-11-20 22:28 ` Tony Lindgren
2014-11-21 8:05 ` Lokesh Vutla
2014-11-21 8:05 ` Lokesh Vutla
2014-11-21 17:18 ` Tony Lindgren
2014-11-21 17:18 ` Tony Lindgren
2014-11-21 9:15 ` Roger Quadros
2014-11-21 9:15 ` Roger Quadros
2014-11-21 11:15 ` Arnd Bergmann
2014-11-21 11:15 ` Arnd Bergmann
2014-11-21 16:18 ` Tony Lindgren [this message]
2014-11-21 16:18 ` Tony Lindgren
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=20141121161821.GS7046@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.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 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.