From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Organization: CC CTU Prague
To: rusty@rustcorp.com.au
Date: Wed, 13 Nov 2002 19:36:23 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Modules in 2.5.47-bk...
Cc: kaos@ocs.com.au, linux-kernel@vger.kernel.org
Message-ID: <76A6C122742@vcnet.vc.cvut.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1608
Lines: 32

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.

  For now I gave up. Except other, I did not found way how to pass
options to module: MODULE_PARM() is now always nothing, and
while options are probably stored in THIS_MODULE->args, I see
no users of this (load_module finds .setup.init (which is now named
.init.setup, and __setup expands to it only ifndef MODULE, BTW!), but 
ignores it afterward).

  So in short, is there available some document which says why this
change was needed, where it is going, and what fs and device driver
developers (ie. me) should do to get their (ie. mine) drivers back 
to working state? Should I just concentrate on my other projects,
and stop tracking 2.5.x kernels? Or should I just do couple of
cset -x ?
                                            Thanks,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/