2.4.13-pre4 | i2o_pci.c:165 structure has no member named `pdev'
Kernel 2.4.13-pre4
make[3]: Entering directory `/usr/local/src/linux/drivers/message/i2o'
gcc -D__KERNEL__ -I/usr/local/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DEXPORT_SYMTAB -c i2o_pci.ci2o_pci.c: In function `i2o_pci_install':
i2o_pci.c:165: structure has no member named `pdev'
...
c->bus.pci.irq = -1;
c->bus.pci.queue_buggy = 0;
c->bus.pci.dpt = 0;
c->bus.pci.short_req = 0;
c->bus.pci.pdev = dev;
Has someone already fixed this before I start digging?
David
It looks like this has been an issue since -pre1 -- we've seen this too with i2o as a module. Between .11 and the parport issue with .12, it's certainly been interesting recently. :)
Anyone have any news on this? Sorry if I've missed it.
Thanks much,
Signature · 2 lines
Ken. [email protected]
On Thu, Oct 18, 2001 at 05:08:18PM -0400, David Ford wrote:
| Kernel 2.4.13-pre4 | | make[3]: Entering directory `/usr/local/src/linux/drivers/message/i2o' | gcc -D__KERNEL__ -I/usr/local/src/linux/include -Wall | -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer | -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 | -march=i586 -DEXPORT_SYMTAB -c i2o_pci.c | i2o_pci.c: In function `i2o_pci_install': | i2o_pci.c:165: structure has no member named `pdev' | | ... | c->bus.pci.irq = -1; | c->bus.pci.queue_buggy = 0; | c->bus.pci.dpt = 0; | c->bus.pci.short_req = 0; | c->bus.pci.pdev = dev; | | Has someone already fixed this before I start digging? | | David | | | - | To unsubscribe from this list: send the line "unsubscribe linux-kernel" in | the body of a message to [email protected] | More majordomo info at http://vger.kernel.org/majordomo-info.html | Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines
It looks like this has been an issue since -pre1 -- we've seen this too with i2o as a module. Between .11 and the parport issue with .12, it's certainly been interesting recently. :)
Anyone have any news on this? Sorry if I've missed it.
Its broken until I finish merging the i2o changes with Linus. Its ok in the -ac tree and indeed you can use the -ac changes to get to where I should be merge dwith Linus
According to a few posts the last few days, it's part of an incomplete merge betwixt -ac and linus. I assume it will get completed shortly.
David
Quoted 8 lines · Ken Brownfield
It looks like this has been an issue since -pre1 -- we've seen this too with i2o as a module. Between .11 and the parport issue with .12, it's certainly been interesting recently. :)
Anyone have any news on this? Sorry if I've missed it.
Thanks much,