Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753171Ab0AGSKO (ORCPT ); Thu, 7 Jan 2010 13:10:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753138Ab0AGSKM (ORCPT ); Thu, 7 Jan 2010 13:10:12 -0500 Received: from xenotime.net ([72.52.64.118]:57800 "HELO xenotime.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753101Ab0AGSKL (ORCPT ); Thu, 7 Jan 2010 13:10:11 -0500 Date: Thu, 7 Jan 2010 10:10:06 -0800 From: Randy Dunlap To: Stephen Rothwell , linux-kbuild@vger.kernel.org Cc: linux-next@vger.kernel.org, LKML , Valdis.Kletnieks@vt.edu Subject: Re: linux-next: Tree for January 7 (pcmcia) Message-Id: <20100107101006.e59989a8.rdunlap@xenotime.net> In-Reply-To: <20100107172134.af71c742.sfr@canb.auug.org.au> References: <20100107172134.af71c742.sfr@canb.auug.org.au> Organization: YPO4 X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.0; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 35 On Thu, 7 Jan 2010 17:21:34 +1100 Stephen Rothwell wrote: > Hi all, > > Changes since 20100106: drivers/built-in.o: In function `yenta_probe': yenta_socket.c:(.devinit.text+0x1e582): undefined reference to `pccard_nonstatic_ops' CONFIG_PCCARD=y CONFIG_PCMCIA=m CONFIG_PCCARD_NONSTATIC=m CONFIG_YENTA=y so yenta code (built-in) tries to reference data that lives in a loadable module. But I would expect this Kconfig: config YENTA tristate "CardBus yenta-compatible bridge support" depends on PCI select CARDBUS if !EMBEDDED select PCCARD_NONSTATIC if PCMCIA to make PCCARD_NONSTATIC=y instead of =m. Has something changed in kconfig recently that would make that different? --- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/