linux-kernel - Re: linux-next: Tree for May 7 (argh)

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: <536A9CF2.90906@infradead.org>
Date:	Wed, 07 May 2014 13:52:02 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
CC:	linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for May 7 (argh)

On 05/07/2014 12:33 AM, Stephen Rothwell wrote:
> Hi all,
> 
> This tree still fails (more than usual) the powerpc allyesconfig build
> and also the celleb_defconfig.
> 
> Changes since 20140506:
> 

I was away for one week.  Did I miss some new instructions about
building linux-next?

I get a thousands of messages like these:

WARNING: "system_wq" [drivers/misc/bh1770glc.ko] has no CRC!
WARNING: "__wake_up" [drivers/misc/bh1770glc.ko] has no CRC!
WARNING: "sysfs_notify" [drivers/misc/bh1770glc.ko] has no CRC!
WARNING: "kfree" [drivers/misc/bh1770glc.ko] has no CRC!


Also there hundreds of messages like these:

ps2mult.c:(.exit.text+0x8f): multiple definition of `cleanup_module'
ps2mult.c:(.init.text+0xbc8): multiple definition of `init_module'
ipack.c:(.exit.text+0x0): multiple definition of `cleanup_module'
ipack.c:(.init.text+0x0): multiple definition of `init_module'
mcb-core.c:(.text+0x40d): multiple definition of `cleanup_module'
mcb-core.c:(.text+0x3fb): multiple definition of `init_module'



Thanks!
-- 
~Randy
--
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/