From: Jesse Barnes <jbarnes@engr.sgi.com>
To: John Rose <johnrose@austin.ibm.com>
Cc: Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] release_pcibus_dev() crash
Date: Thu, 13 Jan 2005 09:33:58 -0800 [thread overview]
Message-ID: <200501130933.59041.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1105636311.30960.8.camel@sinatra.austin.ibm.com>
On Thursday, January 13, 2005 9:11 am, John Rose wrote:
> Jesse-
>
> I'm having trouble with enabling the legacy PCI stuff. I added #define
> HAVE_PCI_LEGACY to pci.h, but probe.c doesn't build:
>
> drivers/pci/probe.c: In function `pci_create_legacy_files':
> drivers/pci/probe.c:50: error: `pci_read_legacy_io' undeclared (first
> use in this function)
> drivers/pci/probe.c:50: error: (Each undeclared identifier is reported
> only oncedrivers/pci/probe.c:50: error: for each function it appears
> in.)
> drivers/pci/probe.c:51: error: `pci_write_legacy_io' undeclared (first
> use in this function)
> drivers/pci/probe.c:60: error: `pci_mmap_legacy_mem' undeclared (first
> use in this function)
>
> Am I missing something obvious? :)
Maybe, did you read Documentation/filesystems/sysfs-pci.c? You need to do
more than just enable HAVE_PCI_LEGACY, you also need to implement some
functions.
Jesse
next prev parent reply other threads:[~2005-01-13 17:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 0:39 John Rose
2005-01-13 0:55 ` Jesse Barnes
2005-01-13 17:11 ` John Rose
2005-01-13 17:33 ` Jesse Barnes [this message]
2005-01-13 17:49 ` John Rose
2005-01-13 18:18 ` Greg KH
2005-01-13 18:21 ` Jesse Barnes
2005-01-13 18:37 ` Greg KH
2005-01-13 20:12 ` John Rose
2005-01-13 20:25 ` Greg KH
2005-01-13 20:54 ` John Rose
2005-01-13 21:05 ` Greg KH
2005-01-13 21:17 ` John Rose
2005-01-13 21:55 ` John Rose
2005-01-13 23:41 ` Greg KH
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=200501130933.59041.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=greg@kroah.com \
--cc=johnrose@austin.ibm.com \
--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
Powered by JetHome