linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Melchior FRANZ <mfranz@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-rc3
Date: Fri, 23 May 2003 09:00:12 +0200	[thread overview]
Message-ID: <200305230900.18528@pflug3.gphy.univie.ac.at> (raw)

* Marcelo Tosatti -- Friday 23 May 2003 00:47:
> Here goes the third release candidate of 2.4.21.

o The i2c "Philips style parallel port adapter" is only selectable
  as a module in "make menuconfig", although the help text suggests
  that it can be compiled in.

o With all i2c options activated, I still get this:
  drivers/i2c/i2c.o: In function `scx200_i2c_setscl':
  drivers/i2c/i2c.o(.text+0x636f): undefined reference to `scx200_gpio_base'
  drivers/i2c/i2c.o(.text+0x6396): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o(.text+0x63a1): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o(.text+0x63b4): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o: In function `scx200_i2c_setsda':
  drivers/i2c/i2c.o(.text+0x63cf): undefined reference to `scx200_gpio_base'
  drivers/i2c/i2c.o(.text+0x63f6): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o(.text+0x6401): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o(.text+0x6414): undefined reference to `scx200_gpio_shadow'
  drivers/i2c/i2c.o: In function `scx200_i2c_getscl':
  drivers/i2c/i2c.o(.text+0x6423): undefined reference to `scx200_gpio_base'
  drivers/i2c/i2c.o: In function `scx200_i2c_getsda':
  drivers/i2c/i2c.o(.text+0x6463): undefined reference to `scx200_gpio_base'
  drivers/i2c/i2c.o: In function `scx200_i2c_init':
  drivers/i2c/i2c.o(.text+0x64f0): undefined reference to `scx200_gpio_base'
  drivers/i2c/i2c.o(.text+0x655b): undefined reference to `scx200_gpio_configure'
  drivers/i2c/i2c.o(.text+0x6578): undefined reference to `scx200_gpio_configure'

o Some help texts are missing, e.g for
  "Generic PCI IDE Chipset Support"
  i2c/"NatSemi SCx200 I2C using GPIO pins"

Apart from that, 2.4.21-rc3 compiles, boots and runs OK.

m.

             reply	other threads:[~2003-05-23  9:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  7:00 Melchior FRANZ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-26 14:00 Linux 2.4.21-rc3 Andrzej Krzysztofowicz
2003-05-26 17:53 ` Santiago Garcia Mantinan
2003-05-30 20:55   ` Krzysiek Taraszka
2003-05-30 20:23     ` Alan Cox
2003-05-23 12:42 Martijn Uffing
2003-05-23 13:10 ` Carl-Daniel Hailfinger
2003-05-23 13:30   ` Martijn Uffing
2003-05-23 15:00   ` Matthias Andree
2003-05-26 17:11   ` Alan Cox
2003-05-22 22:19 Marcelo Tosatti
2003-05-22 23:46 ` J.A. Magallon
2003-05-26 17:04   ` Alan Cox
2003-05-23  0:51 ` Barry K. Nathan
2003-05-23  5:32   ` Marc-Christian Petersen
2003-05-23  8:27 ` Benjamin Herrenschmidt
2003-05-26 13:16 ` Santiago Garcia Mantinan
2003-05-27  1:14   ` Jeff Chua

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=200305230900.18528@pflug3.gphy.univie.ac.at \
    --to=mfranz@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 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).