public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Grega Fajdiga <Gregor.Fajdiga@guest.arnes.si>,
	Nicolas Boichat <nicolas@boichat.ch>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Compile error in 2.6.8-rc2-mm1 - rivafb related
Date: Fri, 30 Jul 2004 16:14:41 +0200	[thread overview]
Message-ID: <20040730141441.GA685@fs.tum.de> (raw)
In-Reply-To: <1091105305.11537.6.camel@cable155-82.ljk.voljatel.net>

On Thu, Jul 29, 2004 at 02:52:25PM +0200, Grega Fajdiga wrote:

> Good day,

Hi Grega,

> Please CC me, since I'm not subscribed. 
> I just tried to compile 2.6.8-rc2-mm1 and got this error:
> drivers/built-in.o(.text+0x7e369): In function `rivafb_probe'::
> undefined reference to `riva_create_i2c_busses'
> drivers/built-in.o(.text+0x7e4c1): In function `rivafb_probe'::
> undefined reference to `riva_delete_i2c_busses'
> drivers/built-in.o(.exit.text+0x1ca): In function `rivafb_remove'::
> undefined reference to `riva_delete_i2c_busses'
> make: *** [.tmp_vmlinux1] Error 1
>...

thanks for this report.

@Nicolas:
Your rivafb-i2c-fixes patch in -mm causes this with CONFIG_FB_RIVA_I2C=n 
(it moves i2c code from inside an #ifdef CONFIG_FB_RIVA_I2C to a place 
where it isn't guarded by such an #ifdef).

> Thanks,
> Grega

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2004-07-30 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 12:52 Compile error in 2.6.8-rc2-mm1 - rivafb related Grega Fajdiga
2004-07-29 13:02 ` Paulo Marques
     [not found] ` <20040729131507.GS2349@fs.tum.de>
2004-07-30 12:46   ` Grega Fajdiga
2004-07-30 14:14 ` Adrian Bunk [this message]
2004-07-30 16:06   ` Nicolas Boichat
2004-07-30 19:06     ` Adrian Bunk

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=20040730141441.GA685@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=Gregor.Fajdiga@guest.arnes.si \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas@boichat.ch \
    /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