From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.75: parse error in pci.h if !CONFIG_PCI
Date: Sun, 13 Jul 2003 23:07:54 -0700 [thread overview]
Message-ID: <20030714060754.GA20416@kroah.com> (raw)
In-Reply-To: <20030713102740.GY12104@fs.tum.de>
On Sun, Jul 13, 2003 at 12:27:41PM +0200, Adrian Bunk wrote:
> I got the following compile error when trying to compile 2.5.75 with
> !CONFIG_PCI:
>
> <-- snip -->
>
> ...
> CC drivers/message/fusion/mptscsih.o
> In file included from drivers/message/fusion/linux_compat.h:10,
> from drivers/message/fusion/mptbase.h:58,
> from drivers/message/fusion/mptscsih.c:82:
> include/linux/pci.h:718: error: syntax error before "int"
> drivers/message/fusion/mptscsih.c:6924: warning: `mptscsih_setup'
> defined but not used
> make[3]: *** [drivers/message/fusion/mptscsih.o] Error 1
>
> <-- snip -->
Thanks, the patch below should fix this problem. I'll send it on to
Linus in a bit.
greg k-h
# PCI: fix up error for when CONFIG_PCI=n and scsi.h is included.
diff -Nru a/include/linux/pci.h b/include/linux/pci.h
--- a/include/linux/pci.h Sun Jul 13 23:07:44 2003
+++ b/include/linux/pci.h Sun Jul 13 23:07:44 2003
@@ -715,7 +715,6 @@
static inline int pci_assign_resource(struct pci_dev *dev, int i) { return -EBUSY;}
static inline int pci_register_driver(struct pci_driver *drv) { return 0;}
static inline void pci_unregister_driver(struct pci_driver *drv) { }
-static inline int scsi_to_pci_dma_dir(unsigned char scsi_dir) { return scsi_dir; }
static inline int pci_find_capability (struct pci_dev *dev, int cap) {return 0; }
static inline const struct pci_device_id *pci_match_device(const struct pci_device_id *ids, const struct pci_dev *dev) { return NULL; }
next prev parent reply other threads:[~2003-07-14 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 10:27 2.5.75: parse error in pci.h if !CONFIG_PCI Adrian Bunk
2003-07-14 6:07 ` Greg KH [this message]
2003-07-14 18:36 ` Adrian Bunk
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=20030714060754.GA20416@kroah.com \
--to=greg@kroah.com \
--cc=bunk@fs.tum.de \
--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