public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Alexey Korolev <akorolev@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: David Woodhouse <dwmw2@infradead•org>,
	linux-next@vger•kernel.org, Russell King <rmk@arm•linux.org.uk>
Subject: Re: linux-next: mtd tree build failure
Date: Sat, 9 Aug 2008 21:41:35 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0808092131550.3488@casper.infradead.org> (raw)
In-Reply-To: <20080808001939.574e7fad.sfr@canb.auug.org.au>

Hi Stephen,

Thanks for catching export symbol problem.  
Hmm, it seems very strange why i2c_dev.c can't reference the exported symbols. 
We are looking after of the problem. I believe it will be fixed ASAP.

Thanks,
Alexey

> Hi Dave,
> 
> On Thu, 7 Aug 2008 13:30:05 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> > 
> > ERROR: "qry_present" [drivers/mtd/chips/cfi_probe.ko] undefined!
> > ERROR: "qry_mode_off" [drivers/mtd/chips/cfi_probe.ko] undefined!
> > ERROR: "qry_mode_on" [drivers/mtd/chips/cfi_probe.ko] undefined!
> > 
> > Caused by commit 2e489e077a6ad118c4f247faedf330117b107cce ("[MTD] [NOR]
> > Add qry_mode_on()/qry_omde_off() to deal with odd chips").
> 
> Also from an arm cam60_defconfig build:
> 
> drivers/built-in.o: In function `cfi_probe_chip':
> i2c-dev.c:(.text+0x497a4): undefined reference to `qry_mode_on'
> i2c-dev.c:(.text+0x49810): undefined reference to `qry_present'
> i2c-dev.c:(.text+0x49850): undefined reference to `qry_mode_off'
> i2c-dev.c:(.text+0x498a0): undefined reference to `qry_mode_off'
> i2c-dev.c:(.text+0x498b0): undefined reference to `qry_present'
> i2c-dev.c:(.text+0x498c8): undefined reference to `qry_mode_off'
> i2c-dev.c:(.text+0x498d8): undefined reference to `qry_present'
> i2c-dev.c:(.text+0x49ca4): undefined reference to `qry_mode_off'
> 
> This is today's linux-next with these symbols exported (which obviously
> makes no difference here).
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb•auug.org.au
> http://www.canb.auug.org.au/~sfr/
> 

next prev parent reply	other threads:[~2008-08-09 20:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07  3:30 linux-next: mtd tree build failure Stephen Rothwell
2008-08-07 14:19 ` Stephen Rothwell
2008-08-09 20:41   ` Alexey Korolev [this message]
2008-08-09 21:33     ` David Woodhouse
2008-08-11  8:30       ` Alexey Korolev
  -- strict thread matches above, loose matches on Subject: below --
2008-10-20  5:35 Stephen Rothwell
2008-10-20  7:24 ` David Woodhouse
2008-10-20  8:33   ` Mike Rapoport
2008-10-20  8:48     ` David Woodhouse
2009-05-27  3:40 Stephen Rothwell

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=alpine.LFD.1.10.0808092131550.3488@casper.infradead.org \
    --to=akorolev@infradead$(echo .)org \
    --cc=dwmw2@infradead$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rmk@arm$(echo .)linux.org.uk \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox