From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: kaos@ocs.com.au (Keith Owens),
chris@chrullrich.de (Christian Ullrich),
linux-kernel@vger.kernel.org
Subject: Re: insmod problem after modutils upgrading
Date: Thu, 14 Dec 2000 09:32:27 -0300 [thread overview]
Message-ID: <200012141232.eBECWRc30301@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Alan Cox <alan@lxorguk.ukuu.org.uk> of "Wed, 13 Dec 2000 22:13:29 -0000." <E146K9T-0003MT-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> said:
> In-Reply-To: <4381.976745113@ocs3.ocs-net> from "Keith Owens" at Dec 14, 2000 0
> ***9:05:13 AM
> > previously because nobody used those options. Since these are bugs in
> > the modules and only a few modules are affected (less than 5 reported),
> > the fix is to correct the modules that have coding errors.
> That wont be happening in 2.2 until 2.2.19 which probably means 6 months.
> If this is your decision please make it abundantly clear that the new
> modutils are a 2.4 only package.
Why can't you make a fast 2.2.19 with _just_ safe bug fixes (as the fixing
of these module problems certainly is)?
--
Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
-
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-12-14 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 17:41 insmod problem after modutils upgrading Corisen
2000-12-13 20:59 ` Christian Ullrich
2000-12-13 21:04 ` Jeff Garzik
2000-12-13 21:10 ` Alan Cox
2000-12-13 21:11 ` Jeff Garzik
2000-12-13 22:05 ` Keith Owens
2000-12-13 22:13 ` Alan Cox
2000-12-14 0:02 ` Keith Owens
2000-12-14 0:43 ` Alan Cox
2000-12-14 12:32 ` Horst von Brand [this message]
2000-12-14 17:50 ` Alan Cox
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=200012141232.eBECWRc30301@pincoya.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@chrullrich.de \
--cc=kaos@ocs.com.au \
--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;
as well as URLs for NNTP newsgroup(s).