public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: rusty@rustcorp.com.au, kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: Modules in 2.5.47-bk...
Date: Wed, 13 Nov 2002 16:06:03 -0500	[thread overview]
Message-ID: <3DD2BEBB.8040003@pobox.com> (raw)
In-Reply-To: <76A6C122742@vcnet.vc.cvut.cz>

Petr Vandrovec wrote:

> Hi Rusty,
>   I'm probably missing something important, but do you have any plans
> to integrate module-init-tools into modutils, or extend module-init-tools
> functionality to make them usable? I tried module-init-tools 0.6
> and I must say that I'm really surprised that it is possible to make
> such change after feature freeze, without maintaining at least minimal
> usability.
>
>   If there are modutils which can live with new module system, please
> point me to them. But I did not found such.


I'm hoping that Rusty will work with Keith to integrate support for 
2.5.x into the existing modutils package...  it's rather annoying to 
have two totally different modutils when switching between 2.[024].x and 
2.5.x kernels.

/me is building drivers into the kernel for now, which slows down 
debugging, because modules are broken on ia32 and module support isn't 
present on alpha at all anymore [AFAICS]...


  reply	other threads:[~2002-11-13 20:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 18:36 Modules in 2.5.47-bk Petr Vandrovec
2002-11-13 21:06 ` Jeff Garzik [this message]
2002-11-14  3:53   ` Rusty Russell
2002-11-14  4:06     ` Jeff Garzik
2002-11-14  5:22       ` Rusty Russell
2002-11-14 15:45         ` Thierry Vignaud
2002-11-16 13:50           ` Adrian Bunk
2002-11-16 21:08         ` Jeff Garzik
2002-11-14 10:50     ` Christoph Hellwig
2002-11-14 17:53       ` 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=3DD2BEBB.8040003@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=kaos@ocs.com.au \
    --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