From: Dale Amon <amon@vnl.com>
To: linux-kernel@vger.kernel.org
Cc: Frank Davis <fdavis@si.rr.com>
Subject: 2.5.26 : drivers/scsi/BusLogic.c
Date: Thu, 18 Jul 2002 16:45:33 +0100 [thread overview]
Message-ID: <20020718154533.GA6851@vnl.com> (raw)
>As noted below, Frank Davis suggests I fire this back into the
>list for discussion.
>
>On Thu, Jul 18, 2002 at 11:04:17AM -0400, Frank Davis wrote:
>
>>Dale,
>> Here's what I know....
>>not all architectures define an 'address' variable in the struct
>>scatterlist, so some archs will compile with no problems, others won't.
>>If you're using a i386, there isn't an address variable. Here's what I
>>suggest....email linux-kernel with the problem report for 2.5.26, and
>>explain what I have stated above. I could have a bunch of #ifdef for
>>each arch, but thats plain crazy. I'd be interested in what some other
>>developers suggest. Sorry, I couldn't provide you a patch.
>>
>>Regards,
>>Frank
>>
BusLogic.c:32: #error Please convert me to Documentation/DMA-mapping.txt
BusLogic.c: In function `BusLogic_DetectHostAdapter':
BusLogic.c:2841: warning: long unsigned int format, BusLogic_IO_Address_T arg (arg 2)
BusLogic.c: In function `BusLogic_QueueCommand':
BusLogic.c:3415: structure has no member named `address'
BusLogic.c: In function `BusLogic_BIOSDiskParameters':
BusLogic.c:4141: warning: implicit declaration of function `scsi_bios_ptable'
BusLogic.c:4141: warning: assignment makes pointer from integer without a cast
make[2]: *** [BusLogic.o] Error 1
next reply other threads:[~2002-07-18 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 15:45 Dale Amon [this message]
2002-07-18 16:16 ` 2.5.26 : drivers/scsi/BusLogic.c Zwane Mwaikambo
2002-07-19 1:03 ` Doug Ledford
2002-07-19 1:19 ` Doug Ledford
2002-07-19 7:18 ` Michael G. Janicki
2002-07-19 8:41 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 17:00 James Bottomley
2002-07-18 23:24 ` Doug Ledford
2002-07-19 14:30 ` stoffel
2002-07-20 15:14 ` Dale Amon
2002-07-25 14:32 ` Dale Amon
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=20020718154533.GA6851@vnl.com \
--to=amon@vnl.com \
--cc=fdavis@si.rr.com \
--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