From: Lars Duesing <ld@stud.fh-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1: include/linux/pci.h inconsistency?
Date: 14 Jul 2003 17:06:06 +0200 [thread overview]
Message-ID: <1058195165.4131.6.camel@ws1.intern.stud.fh-muenchen.de> (raw)
Hi people!
After having problems compiling nforce2-drivers for 2.6.0-test1, I had a
look after include/linux/pci.h.
There is some inconsistency in there:
pci_driver->driver_data is not there any more BUT in pci_dynids it is
referenced:
unsigned int use_driver_data:1; /* pci_driver->driver_data is
used */
attached a dirty patch:
diff -u linux-2.6.0-test1/include/linux/pci.h
linux-2.6.0-test1.new/include/linux/pci.h
--- linux-2.6.0-test1/include/linux/pci.h 2003-07-14
05:34:02.000000000 +0200
+++ linux-2.6.0-test1.new/include/linux/pci.h 2003-07-14
16:48:30.000000000 +0200
@@ -501,7 +501,7 @@
struct pci_dynids {
spinlock_t lock; /* protects list, index */
struct list_head list; /* for IDs added at runtime */
- unsigned int use_driver_data:1; /* pci_driver->driver_data is
used */
+ unsigned int use_driver_data:0; /* pci_driver->driver_data is
NOT there any more */
};
btw: this driver_data is used by the networking part of the
nforce2-driver. If anybody knows a hint, tell me.
Else I will try to wake up someone at nvidia.
Greetings,
Lars Duesing
Munich University Of Applied Sciences, Students' Council
next reply other threads:[~2003-07-14 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 15:06 Lars Duesing [this message]
2003-07-14 15:40 ` Jeff Garzik
2003-07-15 13:27 ` Marcelo Penna Guerra
2003-07-15 14:42 ` Jeff Garzik
2003-07-15 23:59 ` Marcelo Penna Guerra
2003-07-16 1:49 ` Rahul Karnik
2003-07-15 17:25 Lars Duesing
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=1058195165.4131.6.camel@ws1.intern.stud.fh-muenchen.de \
--to=ld@stud.fh-muenchen.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
all inboxes | Powered by JetHome®