public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updated parameter and modules rewrite (2.4.14)
Date: Fri, 23 Nov 2001 15:15:30 +0100	[thread overview]
Message-ID: <3BFE5A02.76AE6DF8@evision-ventures.com> (raw)
In-Reply-To: <E166p1R-0004ll-00@wagner>

Rusty Russell wrote:
> 
> Hi all,
> 
>    http://ftp.kernel.org/pub/linux/kernel/people/rusty
> 
>         Unified boot/module parameter and module loader rewrite
> updated to 2.4.14.  I'm off to Linux Kongress, so I'll be difficult to
> contact for 10 days or so.
> 
> Main TODOS:
>         1) Should the PARAM() macros also declare the variables?
>                 Lots of people seem to like writing INT_MODULE_PARM macros...
> 
>         2) Need a less-sucky /proc|/proc/sys patch, to add access to
>            parameters through that.


I did have a look at it and I would like to express my full
encouragements
to yours efforts. Finally somebody out there caring about modularization
of the kernel, who doesn't continuously introduce sick stuff like...

We remember:

1. Highjacking System V IPC for autoloader communication.

2. "Persistant module storage" patches, which destabilize the
   kernel.

3. inter_module* idiocy.

4. Overloaded system calls.

      parent reply	other threads:[~2001-11-23 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  8:15 [PATCH] Updated parameter and modules rewrite (2.4.14) Rusty Russell
2001-11-22 10:08 ` Christoph Hellwig
2001-11-23  1:28   ` Rusty Russell
2001-11-23 14:15 ` Martin Dalecki [this message]

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=3BFE5A02.76AE6DF8@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=dalecki@evision.ag \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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