public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new module format
Date: Fri, 19 Jul 2002 18:42:11 +1000	[thread overview]
Message-ID: <20020719184211.4440e6cb.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0207161446400.8911-100000@serv>

On Tue, 16 Jul 2002 15:04:36 +0200 (CEST)
Roman Zippel <zippel@linux-m68k.org> wrote:

> Hi,
> 
> Below is an (unfinished) patch, which makes a small but important change
> to the module format. The module structure is no longer generated by
> insmod and is instead under control of the kernel now. This means we have
> now the freedom to properly cleanup the module code without needing to
> tell insmod about it. The dependency between insmod and the kernel is
> greatly reduced by this.

Um, Hi Roman,

	I've started updating my in-kernel module loader patches for 2.5.26.
I'll send you a mail when it's done.

Thanks,
Rusty.
-- 
   there are those who do and those who hang on and you don't see too
   many doers quoting their contemporaries.  -- Larry McVoy

  parent reply	other threads:[~2002-07-19  8:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 13:04 [RFC] new module format Roman Zippel
2002-07-17 18:54 ` Daniel Phillips
2002-07-17 20:12   ` Roman Zippel
2002-07-17 20:34     ` Daniel Phillips
2002-07-17 22:45       ` Roman Zippel
2002-07-17 23:47         ` Daniel Phillips
2002-07-18 10:01           ` Roman Zippel
2002-07-18 11:09             ` Daniel Phillips
2002-07-18 12:02               ` Roman Zippel
2002-07-18 12:13                 ` Daniel Phillips
2002-07-19  8:42 ` Rusty Russell [this message]
2002-07-19  9:31   ` Roman Zippel
2002-07-20  4:13     ` Rusty Russell

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=20020719184211.4440e6cb.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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