All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
	arashi@arashi.yi.org
Subject: Re: [PATCH] mii module broken under new scheme
Date: Tue, 19 Nov 2002 19:46:31 +0000	[thread overview]
Message-ID: <14517.1037735191@passion.cambridge.redhat.com> (raw)
In-Reply-To: <7FA0E2B042A@vcnet.vc.cvut.cz>


VANDROVE@vc.cvut.cz said:
>  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.

> Only question is whether we want to have it this way or no.

Some questions you might want to consider before that one:

1. How do we handle "insmod -odummy0 dummy.o ; insmod -odummy1 dummy.o"

2. When does the module name differ from the filename (modulo .o) ?

3. Given your answers to #1 and #2, is the module name redundant anyway?

--
dwmw2



  parent reply	other threads:[~2002-11-19 19:39 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
2002-11-19 19:46 ` David Woodhouse [this message]
  -- 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=14517.1037735191@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=arashi@arashi.yi.org \
    --cc=jgarzik@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.