From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Guo Subject: Re: linux-next: build failure after merge of the mmc tree Date: Mon, 6 Jan 2014 14:30:03 +0800 Message-ID: <20140106063000.GC26128@S2101-09.ap.freescale.net> References: <20131213125716.f432c59bf8782a489400a5a7@canb.auug.org.au> <20131217132838.cc16a4dbac2f4d3218bbed1d@canb.auug.org.au> <20131217031600.GG6691@S2101-09.ap.freescale.net> <20140106172243.8067c8e72c666511129a9701@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from co1ehsobe006.messaging.microsoft.com ([216.32.180.189]:52000 "EHLO co1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751218AbaAFG3z (ORCPT ); Mon, 6 Jan 2014 01:29:55 -0500 Content-Disposition: inline In-Reply-To: <20140106172243.8067c8e72c666511129a9701@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Dong Aisheng , Chris Ball , linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" , Dong Aisheng Hi Stephen, On Mon, Jan 06, 2014 at 05:22:43PM +1100, Stephen Rothwell wrote: > Hi all, > > On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng wrote: > > > > I tested that Chris tree does not have problem. > > It's caused by IMX tree updates. > > > > Chris, > > Is the way Shawn suggested OK for you? > > Can we have some resolution of this please? This failed to build again > today so I have used the version of the mmc tree from next-20131212 > again. I tried the obvious fix (s/pinctrl_usdhc4_1/pinctrl_usdhc4/) but > that didn't work. I'm afraid that using a working mmc tree next branch might be the only option until Chris comes online to drop the patch from his tree. Shawn