linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers: bus: Move the OMAP interconnect driver to drivers/bus/
Date: Thu, 20 Sep 2012 16:54:24 -0700	[thread overview]
Message-ID: <20120920235423.GP28835@atomide.com> (raw)
In-Reply-To: <CAOesGMgzAiFQKpZEpXqRS+U9fxcLAemhb+MCNsn0AOffa6JiNA@mail.gmail.com>

* Olof Johansson <olof@lixom.net> [120920 16:23]:
> On Wed, Sep 19, 2012 at 10:56 PM, Shilimkar, Santosh
> <santosh.shilimkar@ti.com> wrote:
> > On Thu, Sep 20, 2012 at 12:27 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Monday 17 September 2012, Tony Lindgren wrote:
> >>> * Santosh Shilimkar <santosh.shilimkar@ti.com> [120914 02:21]:
> >>> > OMAP interconnect drivers are used for the interconnect error handling.
> >>> > Since they are bus driver, lets move it to newly created drivers/bus.
> >>> >
> >>> > Cc: Arnd Bergmann <arnd@arndb.de>
> >>> > Cc: Tony Lindgren <tony@atomide.com>
> >>> > Tested-by: Lokesh Vutla <lokeshvutla@ti.com>
> >>> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >>> > ---
> >>> > Patch just moves OMAP interconnect drivers as is to the newly created
> >>> > driver/bus/* directory. Patch is generated against "arm-soc/drivers/ocp2scp"
> >>> > tree and test on all OMAP boards.
> >>>
> >>> Great, looks like this should not conflict with other
> >>> omap patches queued, so Arnd should probably take this into
> >>> the bus branch:
> >>>
> >>> Acked-by: Tony Lindgren <tony@atomide.com>
> >>
> >> It turns out that the patch actually did conflict and we now have a broken
> >> omap2plus_defconfig. The patch below seems to fix it, but please verify
> >> that this makes sense.
> >>
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >>
> > Looks correct.
> >
> > Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> 
> I ended up applying something very similar to this and carried the
> ACKs on that, but I broke it up in two pieces; one for the
> drivers/ocp2scp branch to fix the irq numbers, and another to just
> for-next to deal with the soc.h include file (since that should
> probably have been fixed at branch merge time).
> 
> Pushed out to for-next as well.

OK thanks!

Tony

      reply	other threads:[~2012-09-20 23:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  9:20 [PATCH 1/1] drivers: bus: Move the OMAP interconnect driver to drivers/bus/ Santosh Shilimkar
2012-09-17 21:51 ` Tony Lindgren
2012-09-19 14:58   ` Arnd Bergmann
2012-09-19 15:10     ` Olof Johansson
2012-09-19 16:21     ` Shilimkar, Santosh
2012-09-19 18:57   ` Arnd Bergmann
2012-09-19 19:11     ` Tony Lindgren
2012-09-20  5:56     ` Shilimkar, Santosh
2012-09-20 23:22       ` Olof Johansson
2012-09-20 23:54         ` Tony Lindgren [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=20120920235423.GP28835@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=santosh.shilimkar@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 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).