From: Ken Brownfield <brownfld@irridia.com>
To: linux-kernel@vger.kernel.org
Cc: David Ford <david@blue-labs.org>
Subject: Re: [compile bug] 2.4.13-pre4 | i2o_pci.c:165 structure has no member named `pdev'
Date: Fri, 19 Oct 2001 18:56:03 -0500 [thread overview]
Message-ID: <20011019185603.A13465@asooo.flowerfire.com> (raw)
In-Reply-To: <3BCF44C2.5030504@blue-labs.org>
In-Reply-To: <3BCF44C2.5030504@blue-labs.org>; from david@blue-labs.org on Thu, Oct 18, 2001 at 05:08:18PM -0400
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,
--
Ken.
brownfld@irridia.com
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 majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-10-19 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 21:08 [compile bug] 2.4.13-pre4 | i2o_pci.c:165 structure has no member named `pdev' David Ford
2001-10-19 23:56 ` Ken Brownfield [this message]
2001-10-20 0:27 ` David Ford
2001-10-21 15:09 ` Alan Cox
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=20011019185603.A13465@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--cc=david@blue-labs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.