From: Tony Lindgren <tony@atomide.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>, Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH 3/3] drivers: bus: Move omap gpmc code to live under drivers
Date: Fri, 21 Nov 2014 09:18:04 -0800 [thread overview]
Message-ID: <20141121171804.GU7046@atomide.com> (raw)
In-Reply-To: <546EF266.1010901@ti.com>
* Lokesh Vutla <lokeshvutla@ti.com> [141121 00:09]:
> On Friday 21 November 2014 03:58 AM, Tony Lindgren wrote:
> > --- a/drivers/bus/Makefile
> > +++ b/drivers/bus/Makefile
> > @@ -5,7 +5,8 @@
> > obj-$(CONFIG_BRCMSTB_GISB_ARB) += brcmstb_gisb.o
> > obj-$(CONFIG_IMX_WEIM) += imx-weim.o
> > obj-$(CONFIG_MVEBU_MBUS) += mvebu-mbus.o
> > -obj-$(CONFIG_OMAP_OCP2SCP) += omap-ocp2scp.o
>
> I guess this is unrelated to $subject. Shouldn't this be dropped?
Yes thanks for catching that.
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 09:18:04 -0800 [thread overview]
Message-ID: <20141121171804.GU7046@atomide.com> (raw)
In-Reply-To: <546EF266.1010901@ti.com>
* Lokesh Vutla <lokeshvutla@ti.com> [141121 00:09]:
> On Friday 21 November 2014 03:58 AM, Tony Lindgren wrote:
> > --- a/drivers/bus/Makefile
> > +++ b/drivers/bus/Makefile
> > @@ -5,7 +5,8 @@
> > obj-$(CONFIG_BRCMSTB_GISB_ARB) += brcmstb_gisb.o
> > obj-$(CONFIG_IMX_WEIM) += imx-weim.o
> > obj-$(CONFIG_MVEBU_MBUS) += mvebu-mbus.o
> > -obj-$(CONFIG_OMAP_OCP2SCP) += omap-ocp2scp.o
>
> I guess this is unrelated to $subject. Shouldn't this be dropped?
Yes thanks for catching that.
Regards,
Tony
next prev parent reply other threads:[~2014-11-21 17: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 [this message]
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
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=20141121171804.GU7046@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=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.