[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130621065310.GK5523@atomide.com>
Date: Thu, 20 Jun 2013 23:53:10 -0700
From: Tony Lindgren <tony@...mide.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, Suman Anna <s-anna@...com>,
Omar Ramirez Luna <omar.ramirez@...itl.com>,
Loic Pallardy <loic.pallardy@...com>
Subject: Re: linux-next: manual merge of the arm-soc tree with the mailbox
tree
* Stephen Rothwell <sfr@...b.auug.org.au> [130620 23:48]:
> Hi all,
>
> On Fri, 21 Jun 2013 16:26:56 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Today's linux-next merge of the arm-soc tree got a conflict in
> > drivers/mailbox/Kconfig between commit a1824eaab70f ("mailbox: OMAP:
> > introduce mailbox framework") from the mailbox tree and commit
> > c869c75c16b3 ("mailbox/omap: move the OMAP mailbox framework to drivers")
> > from the arm-soc tree.
> >
> > I fixed it up (I suspect not properly - see below) and can carry the fix
> > as necessary (no action is required).
> >
> > It looks like we have two different versions of these changes in
> > linux-next now, so please clean it all up. i.e. can I just drop the
> > mailbox tree now?
>
> OK, things went steeply downhill from here, so I went back and removed
> the mailbox tree ...
I think Olof dropped the earlier version of the mailbox branch, and
remerged the updated mailbox branch. So if there was also yet another
mailbox branch being pulled into Linux next, then yes, dropping it is
the way to go.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists