From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: undefined reference to pci_io_base
Date: Wed, 30 Aug 2006 08:38:36 +1000 [thread overview]
Message-ID: <1156891116.8433.578.camel@localhost.localdomain> (raw)
In-Reply-To: <20060829202831.GB27372@austin.ibm.com>
> > #if defined(CONFI_PCI)
> > extern unsigned long pci_io_base;
> > #else
> > #define pci_io_base 0
> > #endif
>
> This makes the most sense to me; it compiles to something nice.
Agreed.
Ben.
next prev parent reply other threads:[~2006-08-29 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 17:34 undefined reference to pci_io_base Geoff Levand
2006-08-29 20:28 ` Linas Vepstas
2006-08-29 22:38 ` Benjamin Herrenschmidt [this message]
2006-08-29 22:42 ` Paul Mackerras
2006-08-29 23:20 ` Linas Vepstas
2006-08-29 23:57 ` Geoff Levand
2006-08-30 0:13 ` Paul Mackerras
2006-08-30 15:05 ` Geoff Levand
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=1156891116.8433.578.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.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).