All of lore.kernel.org
 help / color / mirror / Atom feed
From: GCS <gcs@lsc.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc4
Date: Tue, 17 Feb 2004 19:45:43 +0100	[thread overview]
Message-ID: <20040217184543.GA18495@lsc.hu> (raw)
In-Reply-To: <Pine.LNX.4.58.0402161945540.30742@home.osdl.org>

Hi Linus,

On Mon, Feb 16, 2004 at 07:51:08PM -0800, Linus Torvalds <torvalds@osdl.org> wrote:
>  I'm planning on doing the final 2.6.3 tomorrow, so please test this 
> final -rc.
> 
> Most notably, this should support ppc/ppc64 out-of-the-box, complete with
> G5 support (64-bit). Special thanks to BenH who made sure the new radeonfb
> driver works on a wide variety of hardware (a number of the fixes here
> relative to -rc3 was making sure the driver works on regular x86 laptops).
 For me on a laptop with integrated Radeon Mobility card:
  LD      .tmp_vmlinux1
drivers/built-in.o(.text+0xb2a03): In function `radeon_setup_i2c_bus':
: undefined reference to `i2c_bit_add_bus'
drivers/built-in.o(.text+0xb2b7a): In function `radeon_delete_i2c_busses':
: undefined reference to `i2c_bit_del_bus'
drivers/built-in.o(.text+0xb2b8a): In function `radeon_delete_i2c_busses':
: undefined reference to `i2c_bit_del_bus'
drivers/built-in.o(.text+0xb2b9a): In function `radeon_delete_i2c_busses':
: undefined reference to `i2c_bit_del_bus'
drivers/built-in.o(.text+0xb2baa): In function `radeon_delete_i2c_busses':
: undefined reference to `i2c_bit_del_bus'
drivers/built-in.o(.text+0xb2c44): In function `radeon_do_probe_i2c_edid':
: undefined reference to `i2c_transfer'
make: *** [.tmp_vmlinux1] Error 1

.config snippshet:
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_DEBUG=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set

Distribution: Debian Sid, gcc is gcc version 3.3.3 20040214 (prerelease)
(Debian)

AFAICR -rc3 was the first version with this problem.

Cheers,
GCS

  parent reply	other threads:[~2004-02-17 19:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  3:51 Linux 2.6.3-rc4 Linus Torvalds
2004-02-17  6:19 ` Felix Seeger
2004-02-17  8:54 ` Martin Diehl
2004-02-17  9:27   ` Martin Diehl
2004-02-17 15:39   ` Bartlomiej Zolnierkiewicz
2004-02-17 16:21 ` Linux 2.6.3-rc4 (compile stats) John Cherry
2004-02-17 18:45 ` GCS [this message]
2004-02-17 19:09   ` Linux 2.6.3-rc4 Linus Torvalds
2004-02-17 20:05     ` Adrian Bunk
2004-02-17 20:16       ` Linus Torvalds
2004-02-17 22:59         ` Adrian Bunk
2004-02-17 23:11           ` Linus Torvalds
2004-02-17 23:37             ` Radeon issue on x86 Benjamin Herrenschmidt
2004-02-18  0:17               ` Linus Torvalds
2004-02-18  0:33                 ` Benjamin Herrenschmidt
2004-02-18  0:00             ` Linux 2.6.3-rc4 Adrian Bunk
2004-02-18  1:28               ` Roman Zippel
2004-02-18  0:39             ` Roman Zippel
2004-02-18  1:06             ` Roman Zippel
2004-02-18  2:45           ` Roman Zippel
2004-02-18  2:58             ` Linus Torvalds
2004-02-18  0:15       ` Roman Zippel
2004-02-18  0:21     ` GCS
2004-02-17 18:56 ` Jonathan Brown
2004-02-17 19:06   ` Linus Torvalds
2004-02-18 10:18   ` Andreas Happe
2004-02-18  4:06 ` 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=20040217184543.GA18495@lsc.hu \
    --to=gcs@lsc.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.