From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: Another problem with Alpha and 2.5.13
Date: Sat, 4 May 2002 19:46:55 +0200 [thread overview]
Message-ID: <000f01c1f393$ae6e2280$1201a8c0@pitzeier.priv.at> (raw)
Hi volks!
Here the problem
raid5.c: In function `raid5_diskop':
raid5.c:1725: dereferencing pointer to incomplete type
raid5.c:1737: dereferencing pointer to incomplete type
raid5.c:1738: dereferencing pointer to incomplete type
raid5.c:1749: dereferencing pointer to incomplete type
raid5.c:1763: dereferencing pointer to incomplete type
raid5.c:1764: dereferencing pointer to incomplete type
raid5.c:1780: dereferencing pointer to incomplete type
raid5.c:1799: dereferencing pointer to incomplete type
raid5.c:1800: dereferencing pointer to incomplete type
raid5.c:1819: dereferencing pointer to incomplete type
raid5.c:1824: dereferencing pointer to incomplete type
raid5.c:1827: dereferencing pointer to incomplete type
raid5.c:1833: dereferencing pointer to incomplete type
raid5.c:1839: dereferencing pointer to incomplete type
raid5.c:1840: dereferencing pointer to incomplete type
raid5.c:1850: dereferencing pointer to incomplete type
raid5.c:1855: dereferencing pointer to incomplete type
raid5.c:1856: dereferencing pointer to incomplete type
raid5.c:1936: dereferencing pointer to incomplete type
raid5.c:1937: dereferencing pointer to incomplete type
raid5.c:1938: dereferencing pointer to incomplete type
raid5.c:1943: dereferencing pointer to incomplete type
raid5.c:1945: dereferencing pointer to incomplete type
raid5.c:1956: dereferencing pointer to incomplete type
raid5.c:1983: dereferencing pointer to incomplete type
raid5.c:1717: warning: `i' might be used uninitialized in this function
raid5.c:1719: warning: `tmp' might be used uninitialized in this
function
raid5.c:1719: warning: `sdisk' might be used uninitialized in this
function
raid5.c:1719: warning: `adisk' might be used uninitialized in this
function
raid5.c: At top level:
raid5.c:1991: warning: initialization from incompatible pointer type
raid5.c:2000: warning: initialization from incompatible pointer type
raid5.c:2002: parse error before `raid5_init'
raid5.c:2003: warning: return type defaults to `int'
make[2]: *** [raid5.o] Error 1
make[2]: Leaving directory `/root/linux-2.5.13/drivers/md'
make[1]: *** [_modsubdir_md] Error 2
make[1]: Leaving directory `/root/linux-2.5.13/drivers'
make: *** [_mod_drivers] Error 2
????
next reply other threads:[~2002-05-04 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 17:46 Oliver Pitzeier [this message]
2002-05-04 17:54 ` Alexander Viro
2002-05-05 12:00 ` Oliver Pitzeier
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='000f01c1f393$ae6e2280$1201a8c0@pitzeier.priv.at' \
--to=o.pitzeier@uptime.at \
--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
all inboxes | Powered by JetHome®