From: Jasper Spaans <spaans@delft.corps.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] raid5 link error? (was [PATCH] raid5 fix after xor.c cleanup)
Date: Sat, 18 Nov 2000 23:53:52 +0100 [thread overview]
Message-ID: <20001118235352.D2226@spaans.ds9a.nl> (raw)
In-Reply-To: <20001117234144.A14461@spaans.ds9a.nl> <20001118123536.A5674@spaans.ds9a.nl>
In-Reply-To: <20001118123536.A5674@spaans.ds9a.nl>; from jasper@spaans.ds9a.nl on Sat, Nov 18, 2000 at 12:35:36PM +0100
On Sat, Nov 18, 2000 at 12:35:36PM +0100, Jasper Spaans wrote:
> Hmm, next time I'll need to eat my own dogfood -- this patch doesn't work,
> it only compiles. Don't use it.
It seems to me the original code was correct, but the linking isn't in the
right order and the initcalls are in the wrong order (ie,
raid5.c::raid5_init() is being called before xor.c::calibrate_xor_block() --
any linking gurus out there who can help me out on this one?
Feeling a bit of a schizo, but getting used to my brown paper bag,
Regards
--
Q_. Jasper Spaans <mailto:jspaans@mediakabel.nl> -o)
`~\ Conditional Access/DVB-C/OpenTV/Unix-adviseur /\\
Mr /\ _\_v
Zap Een ongezellig dure consultant nodig? Mail sales@insultant.nl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-18 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 22:41 [PATCH] raid5 fix after xor.c cleanup Jasper Spaans
2000-11-18 11:35 ` Jasper Spaans
2000-11-18 22:53 ` Jasper Spaans [this message]
2000-11-20 0:41 ` [BUG] raid5 link error? (was [PATCH] raid5 fix after xor.c cleanup) Neil Brown
2000-11-26 2:26 ` [BUG] 2.4.0-test11-ac3 breaks raid autodetect (was Re: [BUG] raid5 link error? (was [PATCH] raid5 fix after xor.c cleanup)) Friedrich Lobenstock
2000-11-27 2:18 ` Neil Brown
2000-11-27 8:12 ` Luca Berra
2000-11-27 10:49 ` [KBUILD] " Christoph Hellwig
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=20001118235352.D2226@spaans.ds9a.nl \
--to=spaans@delft.corps.nl \
--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®