linux-kernel - Re: linux-next: build failure after merge of the final tree (mtd 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: <1267455546.11061.0.camel@macbook.infradead.org>
Date:	Mon, 01 Mar 2010 15:59:06 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: linux-next: build failure after merge of the final tree (mtd
 related)

On Mon, 2010-03-01 at 20:48 +1100, Stephen Rothwell wrote:
> Hi David,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/mtd/nand/r852.o: In function `.sm_sector_valid':
> (.text+0x5c70): multiple definition of `.sm_sector_valid'
> drivers/mtd/nand/sm_common.o:(.text+0x3c8): first defined here
> drivers/mtd/nand/r852.o: In function `.sm_block_erased':
> (.text+0x50dc): multiple definition of `.sm_block_erased'
> drivers/mtd/nand/sm_common.o:(.text+0x2bc): first defined here
> drivers/mtd/nand/r852.o: In function `.sm_block_valid':
> (.text+0x5be8): multiple definition of `.sm_block_valid'
> drivers/mtd/nand/sm_common.o:(.text+0x340): first defined here
> 
> Caused by commit 9fc51a37a8da84618df7584cad67c078317f6720 ("mtd: common
> module for smartmedia/xD support") from the mtd tree.
> 
> I applied the following patch for today.

Thanks. Are you happy carrying those until I get back to civilisation on
Monday?

-- 
dwmw2

--
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/