[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121204110655.GE18368@8bytes.org>
Date: Tue, 4 Dec 2012 12:06:56 +0100
From: Joerg Roedel <joro@...tes.org>
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,
Omar Ramirez Luna <omar.luna@...aro.org>,
Ohad Ben-Cohen <ohad@...ery.com>,
Paul Walmsley <paul@...an.com>,
Mike Turquette <mturquette@...com>
Subject: Re: linux-next: manual merge of the arm-soc tree with the iommu tree
On Tue, Dec 04, 2012 at 03:42:03PM +1100, Stephen Rothwell wrote:
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/mach-omap2/clock44xx_data.c between commit 298ea44f211d ("ARM:
> OMAP4: hwmod data: ipu and dsp to use parent clocks instead of leaf
> clocks") from the iommu tree and commit 13a5b6228679 ("ARM: OMAP44xx:
> clock: drop obsolete clock data") from the arm-soc tree.
>
> I just deleted the file as the latter did and can carry the fix as
> necessary (no action is required).
Ohad, Omar, any comment on this?
Joerg
--
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