From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.1 - intermediate bio stuff..
Date: Sun, 16 Dec 2001 19:21:10 -0700 [thread overview]
Message-ID: <200112170221.fBH2LAx01188@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.33.0112161604030.11129-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0112161604030.11129-100000@penguin.transmeta.com>
Linus Torvalds writes:
> 2.5.1 is hopefully a good interim stage - many block drivers should
> work fine, but many more do not. However, the pre-patches were
> getting largish, so I'd rather do a 2.5.1 than wait for all the
> details.
Trying a quick test-run here:
# modprobe ide-probe-mod
/lib/modules/2.5.1/kernel/drivers/ide/ide-mod.o: unresolved symbol block_ioctl
# modprobe ide-cd
/lib/modules/2.5.1/kernel/drivers/ide/ide-mod.o: unresolved symbol block_ioctl
# modprobe ide-disk
/lib/modules/2.5.1/kernel/drivers/ide/ide-mod.o: unresolved symbol block_ioctl
# modprobe nfs
/lib/modules/2.5.1/kernel/fs/nfs/nfs.o: unresolved symbol seq_escape
/lib/modules/2.5.1/kernel/fs/nfs/nfs.o: unresolved symbol seq_printf
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-12-17 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 0:11 Linus Torvalds
2001-12-17 2:21 ` Richard Gooch [this message]
2001-12-17 2:33 ` Dave Jones
2001-12-17 2:52 ` Craig Christophel
2001-12-17 19:11 ` Domian Validation (Re: 2.5.1 - intermediate bio stuff..) Andre Hedrick
2001-12-18 6:04 ` Troy Benjegerdes
2001-12-18 6:12 ` Linus Torvalds
2001-12-18 6:39 ` Troy Benjegerdes
2001-12-18 6:44 ` Larry McVoy
2001-12-18 12:28 ` Rik van Riel
2001-12-18 13:37 ` [lkml] " Ian Soboroff
2001-12-18 16:43 ` Linus Torvalds
2001-12-18 20:38 ` Larry McVoy
2001-12-18 12:52 ` Matthias Andree
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=200112170221.fBH2LAx01188@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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®