public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: toralf.foerster@gmx.de
Cc: Ingo Molnar <mingo@elte.hu>, WANG Cong <xiyou.wangcong@gmail.com>,
	James.Bottomley@hansenpartnership.com,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mike Travis <travis@sgi.com>
Subject: Re: build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present_map'
Date: Fri, 9 May 2008 19:22:51 +0800	[thread overview]
Message-ID: <20080509112251.GM2543@hacking> (raw)
In-Reply-To: <200805091259.20126.toralf.foerster@gmx.de>

On Fri, May 09, 2008 at 12:59:17PM +0200, =?ISO-8859-1?Q?Toralf_F=F6rster_ wrote:

>ERROR: "i2c_master_send" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_detach_client" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_del_driver" [drivers/media/video/tuner.ko] undefined!
>ERROR: "v4l2_i2c_attach" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_register_driver" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_master_recv" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_probe" [drivers/media/video/tuner.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/xc5000.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tuner-xc2028.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tuner-simple.ko] undefined!
>ERROR: "i2c_clients_command" [drivers/media/common/tuners/tuner-simple.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tea5767.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tea5761.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tda9887.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/tda8290.ko] undefined!
>ERROR: "i2c_transfer" [drivers/media/common/tuners/mt20xx.ko] undefined!
>make[1]: *** [__modpost] Error 1
>make: *** [modules] Error 2

Hmmm, it seems a similar issue has already solved in this thread[1].
Maybe you should try Andrew's patch[2].

Thanks!

1. http://lkml.org/lkml/2008/4/30/77
2. http://lkml.org/lkml/2008/4/30/144

  reply	other threads:[~2008-05-09 11:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  9:13 build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present_map' Toralf Förster
2008-05-09  9:30 ` WANG Cong
2008-05-09  9:58   ` Toralf Förster
2008-05-09 10:16     ` WANG Cong
2008-05-09  9:52 ` WANG Cong
2008-05-09  9:58   ` Ingo Molnar
2008-05-09 10:09     ` WANG Cong
2008-05-09 10:59     ` Toralf Förster
2008-05-09 11:22       ` WANG Cong [this message]
2008-05-09 14:22     ` James Bottomley
2008-05-09 14:47       ` Ingo Molnar
2008-05-09 15:01         ` Alexey Starikovskiy
2008-05-10 13:17         ` Ingo Molnar
2008-05-10 14:01           ` James Bottomley
2008-05-10 14:21             ` James Bottomley
2008-05-10 14:34             ` WANG Cong

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=20080509112251.GM2543@hacking \
    --to=xiyou.wangcong@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=toralf.foerster@gmx.de \
    --cc=travis@sgi.com \
    /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