public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: andersen@codepoet.org
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: drivers missing __devexit_p in 2.4.18pre3
Date: Mon, 14 Jan 2002 05:49:51 -0500	[thread overview]
Message-ID: <3C42B7CF.96032B4D@mandrakesoft.com> (raw)
In-Reply-To: <20020114030734.GB17592@codepoet.org>

Erik Andersen wrote:
> 
> A quick check of the source code shows that the following drivers
> appear to still be lacking the devinit fixes which are needed for
> the kernel to compile when using newer versions of binutils.
> 
> Each of these files probably needs the following (though I'm too
> lazy to do it all myself, since my kernel doesn't use any of this
> stuff):
> 
>         s/remove:\(.*\)/remove:__devexit_p(\1)/g
> 
> drivers/net/wan/dscc4.c
> drivers/net/tokenring/abyss.c
> drivers/net/tokenring/tmspci.c
> drivers/net/pcnet32.c
> drivers/net/sis900.c
> drivers/net/dmfe.c
> drivers/net/rcpci45.c
> drivers/net/hamachi.c
> drivers/net/wireless/orinoco_plx.c

I dunno if all of these qualify as hotplug drivers, needing __devfoo at
all?

-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

      parent reply	other threads:[~2002-01-14 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  3:07 drivers missing __devexit_p in 2.4.18pre3 Erik Andersen
2002-01-14  5:08 ` Keith Owens
2002-01-14 10:49 ` Jeff Garzik [this message]

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=3C42B7CF.96032B4D@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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