linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-rc1
Date: Tue, 22 Apr 2003 19:09:35 +0200 (CEST)	[thread overview]
Message-ID: <20030422.190935.276777773.rene.rebe@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.53L.0304211545580.12940@freak.distro.conectiva>

Hi.

"all-module" config all compiles fine - except:

In file included from amd74xx.c:29:
amd74xx.h:101: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared here (not in a function)
amd74xx.h:101: initializer element is not constant
amd74xx.h:101: (near initialization for `amd74xx_chipsets[5].device')
amd74xx.h:109: initializer element is not constant
amd74xx.h:109: (near initialization for `amd74xx_chipsets[5].enablebits[0]')
amd74xx.h:109: initializer element is not constant
amd74xx.h:109: (near initialization for `amd74xx_chipsets[5].enablebits[1]')
amd74xx.h:109: initializer element is not constant
amd74xx.h:109: (near initialization for `amd74xx_chipsets[5].enablebits')
amd74xx.h:112: initializer element is not constant
amd74xx.h:112: (near initialization for `amd74xx_chipsets[5]')
amd74xx.h:115: `PCI_DEVICE_ID_NVIDIA_NFORCE2_IDE' undeclared here (not in a function)
amd74xx.h:115: initializer element is not constant
amd74xx.h:115: (near initialization for `amd74xx_chipsets[6].device')
amd74xx.h:123: initializer element is not constant
amd74xx.h:123: (near initialization for `amd74xx_chipsets[6].enablebits[0]')
amd74xx.h:123: initializer element is not constant
amd74xx.h:123: (near initialization for `amd74xx_chipsets[6].enablebits[1]')
amd74xx.h:123: initializer element is not constant
amd74xx.h:123: (near initialization for `amd74xx_chipsets[6].enablebits')
amd74xx.h:126: initializer element is not constant
amd74xx.h:126: (near initialization for `amd74xx_chipsets[6]')
amd74xx.h:132: initializer element is not constant
amd74xx.h:132: (near initialization for `amd74xx_chipsets[7]')
amd74xx.c:62: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared here (not in a function)
amd74xx.c:62: initializer element is not constant
amd74xx.c:62: (near initialization for `amd_ide_chips[5].id')
amd74xx.c:62: initializer element is not constant
amd74xx.c:62: (near initialization for `amd_ide_chips[5]')
amd74xx.c:63: `PCI_DEVICE_ID_NVIDIA_NFORCE2_IDE' undeclared here (not in a function)
amd74xx.c:63: initializer element is not constant
amd74xx.c:63: (near initialization for `amd_ide_chips[6].id')
amd74xx.c:63: initializer element is not constant
amd74xx.c:63: (near initialization for `amd_ide_chips[6]')
amd74xx.c:65: initializer element is not constant
amd74xx.c:65: (near initialization for `amd_ide_chips[7]')
amd74xx.c:455: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared here (not in a function)
amd74xx.c:455: initializer element is not constant
amd74xx.c:455: (near initialization for `amd74xx_pci_tbl[5].device')
amd74xx.c:455: initializer element is not constant
amd74xx.c:455: (near initialization for `amd74xx_pci_tbl[5]')
amd74xx.c:456: `PCI_DEVICE_ID_NVIDIA_NFORCE2_IDE' undeclared here (not in a function)
amd74xx.c:456: initializer element is not constant
amd74xx.c:456: (near initialization for `amd74xx_pci_tbl[6].device')
amd74xx.c:456: initializer element is not constant
amd74xx.c:456: (near initialization for `amd74xx_pci_tbl[6]')
amd74xx.c:457: initializer element is not constant
amd74xx.c:457: (near initialization for `amd74xx_pci_tbl[7]')
amd74xx.c:389: warning: `ata66_amd74xx' defined but not used

On: Mon, 21 Apr 2003 15:47:32 -0300 (BRT),
    Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> 
> Here goes the first candidate for 2.4.21.
> 
> Please test it extensively.

Sincerely,
- René

--  
René Rebe - Europe/Germany/Berlin
e-mail:   rene@rocklinux.org, rene.rebe@gmx.net
web:      http://www.rocklinux.org/people/rene http://gsmp.tfh-berlin.de/rene/

Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.

  parent reply	other threads:[~2003-04-22 16:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 18:47 Linux 2.4.21-rc1 Marcelo Tosatti
2003-04-21 19:58 ` Stephan von Krawczynski
2003-04-21 22:49 ` Ben Greear
2003-04-21 23:24   ` Willy Tarreau
2003-04-21 23:10 ` J.A. Magallon
2003-04-21 23:39 ` Linux 2.4.21-rc1 - unresolved Eyal Lebedinsky
2003-04-22  7:15   ` Marc-Christian Petersen
2003-04-23 19:44     ` Bill Davidsen
2003-04-23 19:51     ` Marcelo Tosatti
2003-04-24 11:27       ` Marc-Christian Petersen
2003-04-24 11:32         ` Marc-Christian Petersen
2003-04-24 11:37         ` Christoph Hellwig
2003-05-06  2:48   ` Mike Fedyk
2003-04-22  3:00 ` Linux 2.4.21-rc1 Corey Minyard
2003-04-22 21:49   ` Marcelo Tosatti
2003-04-22 22:54     ` Corey Minyard
2003-04-22 13:42 ` Geert Uytterhoeven
2003-04-22 17:09 ` Rene Rebe [this message]
2003-04-22 19:15 ` Lukasz Trabinski
2003-04-22 22:59 ` J.A. Magallon
2003-04-23  7:59 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Stelian Pop
2003-04-23  8:08 ` Linux 2.4.21-rc1 Jerome Chantelauze
2003-04-23 15:09 ` Athanasius
2003-04-23 20:46 ` Olaf Hering
2003-04-30 21:30   ` Carl-Daniel Hailfinger
2003-04-25  3:06 ` Lucas Correia Villa Real
2003-06-07 19:35   ` Adrian Bunk
2003-06-11  4:27     ` Lucas Correia Villa Real
2003-04-25  3:13 ` Lucas Correia Villa Real
2003-04-25 14:15 ` Andreas Metzler
2003-04-25 14:27   ` Martin Josefsson
2003-04-25 14:46     ` Andreas Metzler
2003-04-25 16:19 ` Zed Pobre
2003-04-25 16:24   ` Marc-Christian Petersen
2003-05-06  2:57 ` Mike Fedyk
     [not found] <cistron.Pine.LNX.4.53L.0304211545580.12940@freak.distro.conectiva>
     [not found] ` <E198M48-0000tC-00@ncc1701.cistron.net>
2003-04-23 15:36   ` Athanasius
2003-04-23 16:40     ` Athanasius
2003-04-25 16:17       ` Bill Davidsen
2003-04-25 20:30         ` Athanasius
2003-05-06  4:30           ` Mike Fedyk

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=20030422.190935.276777773.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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).