linux-kernel - Re: linux-next-20081120 - staging

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: <20081121190229.GD31017@suse.de>
Date:	Fri, 21 Nov 2008 11:02:29 -0800
From:	Greg KH <gregkh@...e.de>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	k.gantzke@...lhaus.de
Subject: Re: linux-next-20081120 - staging - meilhaus driver build fails

On Thu, Nov 20, 2008 at 09:46:45PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
> 
>  next-20081120 kernel randconfig on x86_64 box fails, while !CONFIG_MODULES
> 
> drivers/staging/meilhaus/memain.c: In function 'me_probe_pci':
> drivers/staging/meilhaus/memain.c:425: error: implicit declaration of function '__symbol_get'
> drivers/staging/meilhaus/memain.c:425: warning: cast to pointer from integer of different size
> drivers/staging/meilhaus/memain.c:433: warning: cast to pointer from integer of different size
> drivers/staging/meilhaus/memain.c:453: error: implicit declaration of function '__symbol_put'
> make[3]: *** [drivers/staging/meilhaus/memain.o] Error 1
> 
> the driver uses __symbol_get and __symbol_put instead of marco's symbol_get and symbol_put, 
> I have only build tested the patch.

Ick, the code shouldn't be doing any of this :(

I'll work on fixing this up, thanks for pointing it out.

greg k-h
--
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/