From: Miles Lane <miles@megapathdsl.net>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: 2.5.20-dj2 -- fdomain_stub.c:98: unknown field `abort' specified in initializer
Date: 04 Jun 2002 18:21:16 -0700 [thread overview]
Message-ID: <1023240078.20260.307.camel@agate> (raw)
In-Reply-To: <20020604114635.A26099@eng2.beaverton.ibm.com>
On Tue, 2002-06-04 at 11:46, Patrick Mansfield wrote:
> On Tue, Jun 04, 2002 at 11:42:18AM -0700, Miles Lane wrote:
> > gcc -D__KERNEL__ -I/usr/src/linux-2.5/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DKBUILD_BASENAME=fdomain_stub -c -o fdomain_stub.o fdomain_stub.c
> > fdomain_stub.c:98: unknown field `abort' specified in initializer
> > fdomain_stub.c:98: warning: initialization from incompatible pointer type
> > fdomain_stub.c:98: unknown field `reset' specified in initializer
> > fdomain_stub.c:98: warning: initialization from incompatible pointer type
> > make[3]: *** [fdomain_stub.o] Error 1
> > make[3]: Leaving directory `/usr/src/linux-2.5/drivers/scsi/pcmcia'
>
> You should be able to compile it by setting the
> CONFIG_BROKEN_SCSI_ERROR_HANDLING config option.
Thanks Patrick,
The compile still breaks with that option enabled,
but it looks like that driver still hasn't been
ported to the current 2.5 api.
../fdomain.c: In function `do_fdomain_16x0_intr':
../fdomain.c:1568: structure has no member named `address'
../fdomain.c:1601: structure has no member named `address'
../fdomain.c: In function `fdomain_16x0_queue':
../fdomain.c:1687: structure has no member named `address'
prev parent reply other threads:[~2002-06-05 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 18:42 2.5.20-dj2 -- fdomain_stub.c:98: unknown field `abort' specified in initializer Miles Lane
2002-06-04 18:46 ` Patrick Mansfield
2002-06-05 1:21 ` Miles Lane [this message]
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=1023240078.20260.307.camel@agate \
--to=miles@megapathdsl.net \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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.