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: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
	arashi@arashi.yi.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] mii module broken under new scheme
Date: Tue, 19 Nov 2002 13:42:58 -0500	[thread overview]
Message-ID: <3DDA8632.3090105@pobox.com> (raw)
In-Reply-To: <7FA0E2B042A@vcnet.vc.cvut.cz>

Petr Vandrovec wrote:

> Rusty told me that it is intentional. Add
>
> no_module_init;
>
> at the end of module. He even sent patch which fixes dozen of such
> modules (15 I had on my system...) to Linus, but it get somehow lost.



I know.

I'm hoping Linus intentionally dropped it, because it's silly.  See the 
other message I just posted.  It's redundant because the module loader 
can obviously figure out there is no init nor exit routine.  It's just 
like EXPORT_NO_SYMBOLS: redundant and obvious.

<rant>
Why the fsck is Rusty's new module code requiring all these driver 
changes???  Note from your message above that there are "dozens" of 
modules which worked just fine, but now they need to be changed under 
Rusty's new system.

I thought Rusty's new stuff was going to cause minimal to no driver 
breakage.  You know, at kernel summit there was the thought that we 
should just disable module -un-loading.  I wish he had stuck with that 
simple idea, plus module_param [because MODULE_PARM obviously sucks].
</rant>

	Jeff, grumbling driver author who sees his drivers diverging and 
breaking...







  reply	other threads:[~2002-11-19 18:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 18:14 [PATCH] mii module broken under new scheme Petr Vandrovec
2002-11-19 18:42 ` Jeff Garzik [this message]
2002-11-19 19:46 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 22:23 Rusty Russell
2002-11-19 18:21 Petr Vandrovec
2002-11-19 18:44 ` Jeff Garzik
2002-11-19 22:07   ` Rusty Russell
2002-11-19 21:49 ` Rusty Russell
2002-11-19 17:50 Matt Reppert
2002-11-19 17:51 ` Jeff Garzik
2002-11-19 18:15   ` Matt Reppert
2002-11-19 21:38   ` Rusty Russell
2002-11-19 18:37 ` Jeff Garzik
2002-11-21 21:34   ` Bill Davidsen
2002-11-19 19:29 ` Alan Cox
2002-12-02  4:51 ` 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=3DDA8632.3090105@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=arashi@arashi.yi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.com \
    /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