mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, rth@twiddle.net, bjornw@axis.com,
	davidm@hpl.hp.com, geert@linux-m68k.org, ralf@gnu.org,
	mkp@mkp.net, willy@debian.org, anton@samba.org, gniibe@m17n.org,
	kkojima@rr.iij4u.or.jp, Jeff Dike <jdike@karaya.com>
Subject: Re: Userspace Test Framework for module loader porting
Date: Mon, 6 Jan 2003 11:38:20 -0800	[thread overview]
Message-ID: <15897.56108.201340.229554@napali.hpl.hp.com> (raw)
In-Reply-To: <20030106022803.902F82C0E2@lists.samba.org>

>>>>> On Mon, 06 Jan 2003 13:27:02 +1100, Rusty Russell <rusty@rustcorp.com.au> said:

  Rusty> BTW, the change to use shared objects for modules is going to
  Rusty> be a 2.7 thing: after 10 architectures, MIPS toolchain issues
  Rusty> made it non-trivial.  So the current stuff is what is going
  Rusty> to be there for 2.6, so no point waiting 8)

What about all the problems that Richard Henderson pointed out with
the original in-kernel module loader?  Were those solved?  My gut
feeling is that we really want shared objects for kernel modules on
ia64 (and probably alpha?).

	--david

  reply	other threads:[~2003-01-06 19:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06  2:27 Rusty Russell
2003-01-06 19:38 ` David Mosberger [this message]
2003-01-06 22:41   ` Richard Henderson
2003-01-07  0:37     ` David Mosberger
2003-01-08 11:44       ` Rusty Russell
2003-01-11  1:47         ` David Mosberger
2003-01-13  0:27           ` Rusty Russell
2003-01-13 13:20             ` Maciej W. Rozycki
2003-01-14  0:01               ` Rusty Russell
2003-01-24 18:23                 ` return-type for search_extable() David Mosberger
2003-01-28  4:53                   ` Rusty Russell
2003-01-28  6:14                     ` David Mosberger
2003-01-08 11:21   ` Userspace Test Framework for module loader porting 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=15897.56108.201340.229554@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=anton@samba.org \
    --cc=bjornw@axis.com \
    --cc=davidm@hpl.hp.com \
    --cc=geert@linux-m68k.org \
    --cc=gniibe@m17n.org \
    --cc=jdike@karaya.com \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkp@mkp.net \
    --cc=ralf@gnu.org \
    --cc=rth@twiddle.net \
    --cc=rusty@rustcorp.com.au \
    --cc=willy@debian.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

all inboxes | Powered by JetHome®