From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933211Ab0I0SR7 (ORCPT ); Mon, 27 Sep 2010 14:17:59 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:46497 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932447Ab0I0SR6 (ORCPT ); Mon, 27 Sep 2010 14:17:58 -0400 Date: Mon, 27 Sep 2010 11:18:18 -0700 (PDT) Message-Id: <20100927.111818.149846920.davem@davemloft.net> To: linville@tuxdriver.com Cc: ohad@wizery.com, sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the final tree (net tree related) From: David Miller In-Reply-To: <20100927180412.GD11086@tuxdriver.com> References: <20100927154408.55a28127.sfr@canb.auug.org.au> <20100927180412.GD11086@tuxdriver.com> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) 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 From: "John W. Linville" Date: Mon, 27 Sep 2010 14:04:12 -0400 > Subject: [PATCH] wl12xx: fix separate-object-folder builds > > Make this go away (happens when building with a separate object > directory): > > Assembler messages: > Fatal error: can't create drivers/net/wireless/wl12xx/.tmp_wl12xx_platform_data.o: No such file or directory > drivers/net/wireless/wl12xx/wl12xx_platform_data.c: In function 'wl12xx_get_platform_data': > drivers/net/wireless/wl12xx/wl12xx_platform_data.c:28: error: cannot open drivers/net/wireless/wl12xx/.tmp_wl12xx_platform_data.gcno > drivers/net/wireless/wl12xx/wl12xx_platform_data.c:28: confused by earlier errors, bailing out > > Signed-off-by: John W. Linville > Reported-by: Stephen Rothwell BTW, if this fuglet going to work if the driver is built modular? The idea of this things seems to be to allow arch platform code to call into it to set things. Such calls from arch platform code are going to be "obj-y" So if this is built into the modular driver, I can't see how it can work.