Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933101AbXBRFWP (ORCPT ); Sun, 18 Feb 2007 00:22:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933120AbXBRFWO (ORCPT ); Sun, 18 Feb 2007 00:22:14 -0500 Received: from artemis.sr.unh.edu ([132.177.249.69]:19554 "EHLO artemis.sr.unh.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933101AbXBRFWO (ORCPT ); Sun, 18 Feb 2007 00:22:14 -0500 Date: Sun, 18 Feb 2007 00:22:10 -0500 (EST) From: Kai Germaschewski X-X-Sender: kai@artemis.sr.unh.edu To: Tilman Schmidt cc: Adrian Bunk , Hansjoerg Lipp , gigaset307x-common@lists.sourceforge.net, kkeil@suse.de, kai.germaschewski@gmx.de, isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org Subject: Re: Kbuild problem In-Reply-To: <45D74B46.3090602@imap.cc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 22 On Sat, 17 Feb 2007, Tilman Schmidt wrote: > Alright, then so be it. But that raises another question: > asyncdata.o is only needed for M105 and M101, not for the base > driver. How do I express in Kbuild that asyncdata.o is to be added > to gigaset-y only if CONFIG_GIGASET_M105 and CONFIG_GIGASET_M101 > are not both 'n'? The way this is typically done is via Kconfig. Add a config option ASYNCDATA (actually something more descriptive/specific would be better), add a "select ASYNCDATA" to the config options for m101 and m105, and then you can use CONFIG_ASYNCDATA to decide whether to add asyncdata.o in the Makefile. --Kai - 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/