From: Crutcher Dunnavant <crutcher@datastacks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Whats in the wings for 2.5 (when it opens)
Date: Sat, 22 Sep 2001 11:23:51 -0400 [thread overview]
Message-ID: <20010922112351.D9352@mueller.datastacks.com> (raw)
In-Reply-To: <20010922103100.C9352@mueller.datastacks.com> <28866.1001169893@ocs3.intra.ocs.com.au>
In-Reply-To: <28866.1001169893@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sun, Sep 23, 2001 at 12:44:53AM +1000
++ 23/09/01 00:44 +1000 - Keith Owens:
> On Sat, 22 Sep 2001 10:31:00 -0400,
> Crutcher Dunnavant <crutcher@datastacks.com> wrote:
> >++ 22/09/01 12:59 +1000 - Keith Owens:
> >> Post kbuild 2.5 I will be writing a generic parameter/command line
> >> interface so you can insmod foo bar=99 or boot with foo.bar=99. You
> >> will even be able to boot with foo.bar=99 when foo is a module, insmod
> >> will use the command line as a default set of values.
> >
> >Well, that certainly is clean. How deep does it go?
>
> One level, flat. Module names must be unique, -DKBUILD_OBJECT runs off
> module names.
Yes, but can module names contain periods? If they can, then there can
be a notional heirarchy, and that's really all that's needed.
--
Crutcher <crutcher@datastacks.com>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$
next prev parent reply other threads:[~2001-09-22 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 0:18 Whats in the wings for 2.5 (when it opens) Ed Tomlinson
2001-09-18 1:24 ` David Weinehall
2001-09-18 2:24 ` James Simmons
2001-09-18 10:49 ` Gábor Lénárt
2001-09-18 19:49 ` toon
2001-09-21 19:58 ` Crutcher Dunnavant
2001-09-22 2:59 ` Keith Owens
2001-09-22 14:31 ` Crutcher Dunnavant
2001-09-22 14:44 ` Keith Owens
2001-09-22 15:23 ` Crutcher Dunnavant [this message]
2001-09-22 14:38 ` Arnaldo Carvalho de Melo
2001-09-23 13:42 ` José Luis Domingo López
-- strict thread matches above, loose matches on Subject: below --
2001-09-18 17:23 Grover, Andrew
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=20010922112351.D9352@mueller.datastacks.com \
--to=crutcher@datastacks.com \
--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