From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] unresolved symbol pci_proc_init
Date: Mon, 11 Oct 1999 10:08:50 -0700 [thread overview]
Message-ID: <199910111708.KAA22401@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 11 Oct 1999 04:27:14 PDT." <19991011112714.29613.rocketmail@web502.yahoomail.com>
Ulrich Strelow wrote:
> Hi all,
>
> compiling the current CVS kernel for a non-PCI machine
> like my 715/33 leads to an unresolved symbol message
> for pci_proc_init.
>
> In init/main.c is the following code:
>
> #ifdef CONFIG_GECKO
> gsc_init();
> /*
> ** pci_init() is NOT multi-PCI bus friendly.
> */
> #ifdef CONFIG_PROC_FS
> pci_proc_init();
> #endif
> #else
> #ifdef CONFIG_PCI
> pci_init();
> #endif
> #endif
>
> So pci_proc_init is included even if CONFIG_PCI is not
> set.
Ulrich,
Apologies - that's my fault. I wasn't very clean when changing the ifdefs
to invoke gsc_init(). The ifdef should read:
#if defined(CONFIG_PCI) && defined(CONFIG_PROC_FS)
...
If no one else objects, go ahead and submit that - after you try it. :^)
On the same note, the ifdefs in gsc_init() probably need to
use "defined(CONFIG_PCI)" around the "dino_init()" call...
sorry,
grant
> Ulrich
> __________________________________________________
> Do You Yahoo!?
> Bid and sell for free at http://auctions.yahoo.com
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
Grant Grundler
Communications Infrastructure Computer Operations
+1.408.447.7253
prev parent reply other threads:[~1999-10-11 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-11 11:27 [parisc-linux] unresolved symbol pci_proc_init Ulrich Strelow
1999-10-11 17:08 ` Grant Grundler [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=199910111708.KAA22401@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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