mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Goddard <agoddard@purdue.edu>
To: Florin Iucha <florin@iucha.net>
Cc: Greg KH <greg@kroah.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.73
Date: Sun, 22 Jun 2003 16:17:30 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0306221615230.11747@dust> (raw)
In-Reply-To: <20030622204607.GA16386@iucha.net>

On Sun, 22 Jun 2003, Florin Iucha wrote:

> drivers/built-in.o(.text+0x3106): In function `pci_remove_bus_device':
> : undefined reference to `pci_destroy_dev'
> 
> pci_destroy_dev is defined under CONFIG_HOTPLUG and used outside.
> 
> florin
> 
> PS: I think changeset referenced in 10560659712069@kroah.com
> causes the problem.

An attempt at a fix.  It just moves pci_desroy_dev outside the #ifdef).  
I have no idea if this is the correct way to fix this.  It compiles okay.

diff -Naurp hotplug.c.orig hotplug.c
--- hotplug.c.orig      2003-06-22 16:00:25.000000000 -0500
+++ hotplug.c   2003-06-22 16:01:20.000000000 -0500
@@ -219,6 +219,24 @@ int pci_hotplug (struct device *dev, cha
 
 #endif /* CONFIG_HOTPLUG */

+static void pci_destroy_dev(struct pci_dev *dev)
+{
+       pci_proc_detach_device(dev);
+       device_unregister(&dev->dev);
+
+       /* Remove the device from the device lists, and prevent any 
further
+        * list accesses from this device */
+       spin_lock(&pci_bus_lock);
+       list_del(&dev->bus_list);
+       list_del(&dev->global_list);
+       dev->bus_list.next = dev->bus_list.prev = NULL;
+       dev->global_list.next = dev->global_list.prev = NULL;
+       spin_unlock(&pci_bus_lock);
+
+       pci_free_resources(dev);
+       pci_dev_put(dev);
+}
+
 static void
 pci_free_resources(struct pci_dev *dev)
 {

-- 
Alex Goddard
agoddard@purdue.edu

  reply	other threads:[~2003-06-22 21:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 18:53 Linus Torvalds
2003-06-22 20:06 ` Alex Goddard
2003-06-22 20:15   ` Andrew Morton
2003-06-22 22:53     ` Greg KH
2003-06-22 23:31       ` Andrew Morton
2003-06-22 20:46 ` Florin Iucha
2003-06-22 21:17   ` Alex Goddard [this message]
2003-06-22 21:45     ` Alex Goddard
2003-06-22 21:58     ` Alex Goddard
2003-06-23  2:52       ` Greg KH
2003-06-22 23:44 ` 2.5.73: ALSA ISA pnp_init_resource_table compile errors Adrian Bunk
2003-06-23  0:08   ` Adam Belay
2003-07-03  2:53     ` Adrian Bunk
2003-07-03 19:03       ` Adam Belay
2003-07-04 12:11         ` Adrian Bunk
2003-07-15 22:47           ` Adam Belay
2003-07-16 18:22             ` Adrian Bunk
2003-07-16 18:43               ` Adam Belay
2003-07-19 22:03                 ` Adrian Bunk
2003-07-20  5:59                 ` Jochen Hein
2003-08-09 20:40                 ` Adrian Bunk
2003-06-23  0:31 ` 2.5.73: acorn.c compile error Adrian Bunk
2003-06-23 10:13 ` Linux 2.5.73 - Won't compile using oldconfig - config attached vlad
2003-07-02 14:31   ` John Covici
2003-07-02 16:38     ` Greg KH
2003-06-23 20:32 ` Linux 2.5.73 - keyboard failure, repost no. 3 Terje Fåberg
2003-06-26 20:45   ` Vojtech Pavlik
2003-06-27 14:22     ` Terje Fåberg
2003-06-27 19:03       ` Vojtech Pavlik
2003-06-28  9:11         ` Terje Fåberg
2003-06-28  9:37           ` Vojtech Pavlik
2003-06-28 11:40             ` Terje Fåberg

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=Pine.LNX.4.56.0306221615230.11747@dust \
    --to=agoddard@purdue.edu \
    --cc=florin@iucha.net \
    --cc=greg@kroah.com \
    --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

all inboxes | Powered by JetHome®