linux-kernel - Re: linux-next: build failure after merge of the final tree (net tree related)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100927182546.GE11086@tuxdriver.com>
Date:	Mon, 27 Sep 2010 14:25:47 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	David Miller <davem@...emloft.net>
Cc:	ohad@...ery.com, sfr@...b.auug.org.au, netdev@...r.kernel.org,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (net
 tree related)

On Mon, Sep 27, 2010 at 11:18:18AM -0700, David Miller wrote:
> From: "John W. Linville" <linville@...driver.com>
> 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 <linville@...driver.com>
> > Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> 
> 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.

Dave is right -- these Kconfig dependencies (or lack thereof) seem
to be wrong.  Seems like the OMAP code needs to select the option
for this code?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/