From: Giacomo Catenazzi <cate@debian.org>
To: Marco Colombo <marco@esi.it>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
esr@thyrsus.com, linux-kernel@vger.kernel.org
Subject: Re: Aunt Tillie builds a kernel (was Re: ISA hardware discovery --the elegant solution)
Date: Tue, 15 Jan 2002 14:17:15 +0100 [thread overview]
Message-ID: <3C442BDB.7010008@debian.org> (raw)
In-Reply-To: <fa.g54h1nv.126slpt@ifi.uio.no> <fa.k72pe6v.1tmgn1a@ifi.uio.no>
Marco Colombo wrote:
> Alan, Eric (and others, too), please.
> Of course the autoconfigurator is an useful piece of software.
> And of course Eric is posting to the wrong list here. Kernel developers
> don't need any autoconfigurator at all (yes, it's just "extra state").
The main discussion was in kbuild-devel list.
>
> Eric, Aunt Tillie doesn't need any custom-made, untested, probably not
> working kernel. QA comes at a price. The lastest VM fix may take a while
> to reach mainstream kernels. That's life.
Maybe this force kernel maintainer to merge the tested and trusted
distribution patches into the main kernel's branches.
Anyway, the target of Linux changes. If was a toy for hacker 10 year
ago, maybe in future will be the toy for Aunt Tillies. So:
Forget aunts and the other scenarios of Eric.
Let talk about what autoconfigure can do yet (aka the creation of
a /proc/drivers (better in /dev) with a list of all running
kernel drivers. aka how the modules will be in the next months)
giacomo
next parent reply other threads:[~2002-01-15 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.g54h1nv.126slpt@ifi.uio.no>
[not found] ` <fa.k72pe6v.1tmgn1a@ifi.uio.no>
2002-01-15 13:17 ` Giacomo Catenazzi [this message]
2002-01-15 14:50 ` Aunt Tillie builds a kernel (was Re: ISA hardware discovery --the elegant solution) Marco Colombo
2002-01-15 15:01 ` Giacomo Catenazzi
2002-01-15 15:47 ` Marco Colombo
2002-01-15 10:40 Zwane Mwaikambo
2002-01-15 11:35 ` Reid Hekman
2002-01-16 15:32 ` Bill Davidsen
2002-01-21 14:55 ` Mark H. Wood
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=3C442BDB.7010008@debian.org \
--to=cate@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@esi.it \
/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