linux-kernel - Re: linux-next: Tree for June 4 (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] [day] [month] [year] [list]

Message-ID: <20090604180701.GA24896@suse.de>
Date:	Thu, 4 Jun 2009 11:07:01 -0700
From:	Greg KH <gregkh@...e.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for June 4 (staging)

On Thu, Jun 04, 2009 at 08:56:40AM -0700, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20090603:
> 
> drivers/staging/vt6655/built-in.o: In function `rotr1':
> (.text+0x1a883): multiple definition of `rotr1'
> drivers/staging/rt2860/built-in.o:(.text+0x17a9a): first defined here
> drivers/staging/vt6655/built-in.o: In function `tkip_sbox':
> (.text+0x1a850): multiple definition of `tkip_sbox'
> drivers/staging/rt2860/built-in.o:(.text+0x17a6b): first defined here
> drivers/staging/vt6655/built-in.o: In function `xor_32':
> (.text+0x1e938): multiple definition of `xor_32'
> drivers/staging/rt2860/built-in.o:(.text+0x1803c): first defined here
> drivers/staging/vt6655/built-in.o: In function `xor_128':
> (.text+0x1e910): multiple definition of `xor_128'
> drivers/staging/rt2860/built-in.o:(.text+0x18018): first defined here

Ick, more staging drivers that should not be built-in.  I'll go mess
with some Kconfig options...

thanks,

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/