public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: nForce IDE in 2.5?
Date: Fri, 10 Jan 2003 00:12:42 -0800	[thread overview]
Message-ID: <20030110081242.GA1750@kamui> (raw)
In-Reply-To: <20030110073530.GA6681@kamui>

[-- Attachment #1: Type: text/plain, Size: 2754 bytes --]

Bleh, ignore me. I just read the archives

-Josh

On Thu, Jan 09, 2003 at 11:35:30PM -0800, Joshua M. Kwan wrote:
> It's missing a PCI identifier variable for the chipset itself, and if I 
> knew what its value is supposed to be, or where to put it, I would make 
> a patch for it.. =\
> 
> Attached is the error log from the build. I am using 2.5.x-current...
> 
> Regards
> Josh

> In file included from drivers/ide/pci/nvidia.c:29:
> drivers/ide/pci/nvidia.h:35: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared here (not in a function)
> drivers/ide/pci/nvidia.h:35: initializer element is not constant
> drivers/ide/pci/nvidia.h:35: (near initialization for `nvidia_chipsets[0].device')
> drivers/ide/pci/nvidia.h:43: initializer element is not constant
> drivers/ide/pci/nvidia.h:43: (near initialization for `nvidia_chipsets[0].enablebits[0]')
> drivers/ide/pci/nvidia.h:43: initializer element is not constant
> drivers/ide/pci/nvidia.h:43: (near initialization for `nvidia_chipsets[0].enablebits[1]')
> drivers/ide/pci/nvidia.h:43: initializer element is not constant
> drivers/ide/pci/nvidia.h:43: (near initialization for `nvidia_chipsets[0].enablebits')
> drivers/ide/pci/nvidia.h:46: initializer element is not constant
> drivers/ide/pci/nvidia.h:46: (near initialization for `nvidia_chipsets[0]')
> drivers/ide/pci/nvidia.c: In function `nforce_ratemask':
> drivers/ide/pci/nvidia.c:79: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared (first use in this function)
> drivers/ide/pci/nvidia.c:79: (Each undeclared identifier is reported only once
> drivers/ide/pci/nvidia.c:79: for each function it appears in.)
> drivers/ide/pci/nvidia.c: In function `ata66_nforce':
> drivers/ide/pci/nvidia.c:288: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared (first use in this function)
> drivers/ide/pci/nvidia.c: In function `nforce_init_one':
> drivers/ide/pci/nvidia.c:338: warning: `_MOD_INC_USE_COUNT' is deprecated (declared at include/linux/module.h:419)
> drivers/ide/pci/nvidia.c: At top level:
> drivers/ide/pci/nvidia.c:343: `PCI_DEVICE_ID_NVIDIA_NFORCE_IDE' undeclared here (not in a function)
> drivers/ide/pci/nvidia.c:343: initializer element is not constant
> drivers/ide/pci/nvidia.c:343: (near initialization for `nforce_pci_tbl[0].device')
> drivers/ide/pci/nvidia.c:343: initializer element is not constant
> drivers/ide/pci/nvidia.c:343: (near initialization for `nforce_pci_tbl[0]')
> drivers/ide/pci/nvidia.c:344: initializer element is not constant
> drivers/ide/pci/nvidia.c:344: (near initialization for `nforce_pci_tbl[1]')
> make[3]: *** [drivers/ide/pci/nvidia.o] Error 1
> make[2]: *** [drivers/ide/pci] Error 2
> make[1]: *** [drivers/ide] Error 2
> make: *** [drivers] Error 2




[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-01-10  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10  7:35 nForce IDE in 2.5? Joshua M. Kwan
2003-01-10  8:12 ` Joshua M. Kwan [this message]

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=20030110081242.GA1750@kamui \
    --to=joshk@ludicrus.ath.cx \
    --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