All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: Roberto Nibali <ratz@tac.ch>,
	linux-kernel@vger.kernel.org, Donald Becker <becker@scyld.com>,
	Andrew Morton <andrewm@uow.edu.au>
Subject: Re: Fix for Donald Becker's DP83815 network driver (v1.07)
Date: Fri, 20 Apr 2001 05:57:40 -0400	[thread overview]
Message-ID: <3AE00814.10A87766@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104200244000.5165-100000@age.cs.columbia.edu>

Ion Badulescu wrote:
> On Fri, 20 Apr 2001, Jeff Garzik wrote:
> > > Check again. drivers/net builds a .a, not a .o. Trust me, I've tried.

> > Sure, but if you are patching anyway, it much better to fix that than
> > hack space.c :)
> 
> Well, I remember asking Alan if he'd prefer it done that way, and not
> getting a reply back. So I didn't press further.
> 
> The change to support __init/__exit in drivers/net is a no-brainer, and I
> did test it at the time -- it worked as expected. But it's really up to
> Alan to decide, I couldn't care less to be quite honest.
> 
> In a way I think I understand why he's reluctant: it's very easy to end up
> changing the initialization order by mistake and messing up people's
> network setups.

Sorry, I was talking about a local patch not a global patch.  If a user
must patch their 2.2 kernel to get the starfire driver working anyway,
then adding a change to do s/.a/.o/ on Makefiles would be simple.

That said, a 2.2.20 patch to s/.a/.o/ should not break anything at all. 
All old drivers work as before through the static call chain.  All newer
drivers using module_init/exit simply wind up being initialized after
all static initialization has occurred.  With some subsystems this does
create a chicken-and-egg situation, but not for drivers/net...

-- 
Jeff Garzik       | "The universe is like a safe to which there is a
Building 1024     |  combination -- but the combination is locked up
MandrakeSoft      |  in the safe."    -- Peter DeVries

  reply	other threads:[~2001-04-20  9:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 15:58 Fix for Donald Becker's DP83815 network driver (v1.07) Steve Hill
2001-04-17 16:16 ` Roberto Nibali
2001-04-17 16:30   ` Steve Hill
2001-04-17 17:12     ` Roberto Nibali
2001-04-18 10:25     ` Ion Badulescu
2001-04-18 11:32       ` Steve Hill
2001-04-18 15:14         ` Tim Hockin
2001-04-18 20:33         ` Ion Badulescu
2001-04-18 20:40           ` Steve Hill
2001-04-19 10:54           ` Roberto Nibali
2001-04-19 13:06           ` Roberto Nibali
2001-04-20  5:48             ` Ion Badulescu
2001-04-20  6:30               ` Jeff Garzik
2001-04-20  7:09                 ` Ion Badulescu
2001-04-20  7:31                   ` Jeff Garzik
2001-04-20  9:49                     ` Ion Badulescu
2001-04-20  9:57                       ` Jeff Garzik [this message]
2001-04-20 10:05                         ` Ion Badulescu
2001-04-20 16:10                           ` Roberto Nibali
2001-04-20 16:19                             ` Jeff Garzik
2001-04-20 16:50                               ` Roberto Nibali
2001-04-20 19:27                                 ` Ion Badulescu
2001-04-20  9:03               ` Roberto Nibali
2001-04-20  9:42                 ` Ion Badulescu
2001-04-20 10:12                   ` Roberto Nibali

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=3AE00814.10A87766@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andrewm@uow.edu.au \
    --cc=becker@scyld.com \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ratz@tac.ch \
    /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.