public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Chen <crimsun@email.unc.edu>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.17] net/network.o(.text.lock+0x1a88): undefined reference to `local symbols...
Date: Sun, 23 Dec 2001 06:37:33 -0500	[thread overview]
Message-ID: <20011223113733.GA26429@opeth.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.33.0112231226260.1032-100000@doom.bastun.net> <23624.1009106899@ocs3.intra.ocs.com.au>
In-Reply-To: <23624.1009106899@ocs3.intra.ocs.com.au>

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

On Sun, Dec 23, 2001 at 10:28:19PM +1100, Keith Owens wrote:
> AFAICT dmfe.c is hotplug aware, it has the required probe and remove
> pci_driver functions.  But dmfe_remove_one is defined as __exit instead
> of __devexit, it should probably be changed to __devexit and change
>         remove: dmfe_remove_one
> to
>         remove:         __devexit_p(dmfe_remove_one)
> 
> The dmfe maintainer and/or Jeff Garzik needs to decide.

This is one of the hunks I submitted and is in .17-rc2 but was
removed (along with a bunch of incorrect ones I did, oops) in
-final.

-- 
Dan Chen                 crimsun@email.unc.edu
GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-23 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-23 10:27 [2.4.17] net/network.o(.text.lock+0x1a88): undefined reference to `local symbols Vasil Kolev
2001-12-23 11:11 ` Tobias Ringstrom
2001-12-23 11:31   ` Dave Jones
2001-12-23 11:28 ` Keith Owens
2001-12-23 11:37   ` Dan Chen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-23  3:22 Norbert Veber
2001-12-23  5:18 ` Keith Owens
2001-12-23  8:26   ` Norbert Veber

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=20011223113733.GA26429@opeth.ath.cx \
    --to=crimsun@email.unc.edu \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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