From: Samuel Flory <sflory@rackable.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21pre4aa1
Date: Wed, 05 Feb 2003 15:12:03 -0800 [thread overview]
Message-ID: <3E419A43.7070100@rackable.com> (raw)
In-Reply-To: 20030131014020.GA8395@dualathlon.random
Is the dac960 compile still broken? Or did it break again?
make[3]: Entering directory `/stuff/src/linux-2.4.21-pre4-aa1/drivers/block'
gcc -D__KERNEL__ -I/stuff/src/linux-2.4.21-pre4-aa1/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-nostdinc -iwithprefix include -DKBUILD_BASENAME=DAC960 -DEXPORT_SYMTAB
-c DAC960.c
DAC960.c: In function `DAC960_ProcessCompletedBuffer':
DAC960.c:3029: warning: passing arg 1 of `blk_finished_io' makes pointer
from integer without a cast
DAC960.c:3029: too few arguments to function `blk_finished_io'
make[3]: *** [DAC960.o] Error 1
make[3]: Leaving directory `/stuff/src/linux-2.4.21-pre4-aa1/drivers/block'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/stuff/src/linux-2.4.21-pre4-aa1/drivers/block'
make[1]: *** [_subdir_block] Error 2
make[1]: Leaving directory `/stuff/src/linux-2.4.21-pre4-aa1/drivers'
make: *** [_dir_drivers] Error 2
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-02-05 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 1:40 2.4.21pre4aa1 Andrea Arcangeli
2003-01-31 10:56 ` 2.4.21pre4aa1 Christoph Hellwig
2003-01-31 16:11 ` 2.4.21pre4aa1 Andrea Arcangeli
2003-02-05 23:12 ` Samuel Flory [this message]
2003-02-05 23:16 ` 2.4.21pre4aa1 Andrea Arcangeli
2003-02-05 23:22 ` 2.4.21pre4aa1 Samuel Flory
2003-02-05 23:45 ` 2.4.21pre4aa1 J.A. Magallon
2003-02-06 9:39 ` 2.4.21pre4aa1 - hard lockup (PCnet32 related?) Sergey S. Kostyliov
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=3E419A43.7070100@rackable.com \
--to=sflory@rackable.com \
--cc=andrea@suse.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