From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Ball Subject: Re: linux-next: build failure after merge of the mmc tree Date: Thu, 05 Jun 2014 03:57:58 +0100 Message-ID: <8661kgoyfd.fsf@void.printf.net> References: <20140526140735.3f405672@canb.auug.org.au> <20140602151141.084d3350@canb.auug.org.au> <20140604085222.50916c65@canb.auug.org.au> <86egz4pjjv.fsf@void.printf.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from void.printf.net ([89.145.121.20]:43995 "EHLO void.printf.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751401AbaFEC6C (ORCPT ); Wed, 4 Jun 2014 22:58:02 -0400 In-Reply-To: <86egz4pjjv.fsf@void.printf.net> (Chris Ball's message of "Wed, 04 Jun 2014 20:21:40 +0100") Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Russell King Hi Stephen, On Wed, Jun 04 2014, Chris Ball wrote: > On Tue, Jun 03 2014, Stephen Rothwell wrote: >>> This is back again. I have no idea why I didn't get this failure on >>> Friday. Please, guys, go through your tree and fix this problem once >>> and for all. Grep is your friend. >>> >>> I have used the mmc tree from next-20140522 again for today. >> >> Just wondering if you are even receiving my email? > > Sorry about this, I'm working on it now. This one's fixed in mmc-next now. Thanks, - Chris. -- Chris Ball