From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: linux-next: Tree for Oct 11 (mmc) Date: Tue, 11 Oct 2011 11:49:39 -0700 Message-ID: <4E948FC3.2080801@xenotime.net> References: <20111011201127.455df266dcbffb1d621f8576@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from oproxy6-pub.bluehost.com ([67.222.54.6]:56480 "HELO oproxy6-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755192Ab1JKStl (ORCPT ); Tue, 11 Oct 2011 14:49:41 -0400 In-Reply-To: <20111011201127.455df266dcbffb1d621f8576@canb.auug.org.au> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Stephen Rothwell Cc: linux-next@vger.kernel.org, LKML , linux-mmc@vger.kernel.org, Chris Ball On 10/11/11 02:11, Stephen Rothwell wrote: > Hi all, > > The linux-next tree is now available from > git://github.com/sfrothwell/linux-next.git as a temporary measure while > the kernel.org servers are unavailable. > > It may also turn up on git.kernel.org (depending on the mirroring). The > patch set is still absent, however. > > Changes since 20111007: When CONFIG_BLOCK is not enabled: In file included from next-2011-1011/drivers/mmc/card/sdio_uart.c:43:0: next-2011-1011/include/linux/mmc/card.h:175:12: error: 'DISK_NAME_LEN' undeclared here (not in a function) Deleting the #include fixes the sdio_uart.c build. However, the same problem occurs in mmc/core/core.c: In file included from next-2011-1011/drivers/mmc/core/core.c:30:0: next-2011-1011/include/linux/mmc/card.h:175:12: error: 'DISK_NAME_LEN' undeclared here (not in a function) Should mmc/core/ depend on BLOCK? or should it just be made to build even when BLOCK is not enabled? -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***