From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752798AbaAFGaF (ORCPT ); Mon, 6 Jan 2014 01:30:05 -0500 Received: from mail-qc0-f178.google.com ([209.85.216.178]:63736 "EHLO mail-qc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751218AbaAFGaB (ORCPT ); Mon, 6 Jan 2014 01:30:01 -0500 MIME-Version: 1.0 In-Reply-To: <20140106172243.8067c8e72c666511129a9701@canb.auug.org.au> 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> Date: Mon, 6 Jan 2014 14:30:00 +0800 Message-ID: Subject: Re: linux-next: build failure after merge of the mmc tree From: Dong Aisheng To: Stephen Rothwell Cc: Shawn Guo , Chris Ball , linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" , Dong Aisheng Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shawn, How do you suggest to fix this issue? Can we cook a patch for it directly based on linux-next tree? Regards Dong Aisheng On Mon, Jan 6, 2014 at 2:22 PM, 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. > > -- > Cheers, > Stephen Rothwell sfr@canb.auug.org.au