From: Roman Zippel <zippel@linux-m68k.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new module format
Date: Fri, 19 Jul 2002 11:31:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0207191128030.28515-100000@serv> (raw)
In-Reply-To: <20020719184211.4440e6cb.rusty@rustcorp.com.au>
Hi,
On Fri, 19 Jul 2002, Rusty Russell wrote:
> I've started updating my in-kernel module loader patches for 2.5.26.
> I'll send you a mail when it's done.
The more I think about it, the more I like the idea to go into the other
direction. Most of the module information (e.g. symbols, dependencies)
stored in the kernel can be as well managed in userspace.
bye, Roman
next prev parent reply other threads:[~2002-07-19 9:28 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
2002-07-19 9:31 ` Roman Zippel [this message]
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=Pine.LNX.4.44.0207191128030.28515-100000@serv \
--to=zippel@linux-m68k.org \
--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