linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: linux-next: build failure after merge of the final tree (mtd related)
Date: Mon, 01 Mar 2010 15:59:06 +0100	[thread overview]
Message-ID: <1267455546.11061.0.camel@macbook.infradead.org> (raw)
In-Reply-To: <20100301204844.68915148.sfr@canb.auug.org.au>

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

  reply	other threads:[~2010-03-01 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  9:48 linux-next: build failure after merge of the final tree (mtd related) Stephen Rothwell
2010-03-01 14:59 ` David Woodhouse [this message]
2010-03-01 22:39   ` Stephen Rothwell
2010-03-18 14:39     ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1267455546.11061.0.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).