From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [PATCH] Yet more PCI fixes for 2.5.73
Date: Thu, 26 Jun 2003 17:51:44 -0700 [thread overview]
Message-ID: <10566751041502@kroah.com> (raw)
In-Reply-To: <10566751033776@kroah.com>
ChangeSet 1.1499, 2003/06/26 16:04:19-07:00, greg@kroah.com
[PATCH] PCI Hotplug: acpiphp: add release() callback
drivers/pci/hotplug/acpiphp_core.c | 30 ++++++++++++++++++++++--------
1 files changed, 22 insertions(+), 8 deletions(-)
diff -Nru a/drivers/pci/hotplug/acpiphp_core.c b/drivers/pci/hotplug/acpiphp_core.c
--- a/drivers/pci/hotplug/acpiphp_core.c Thu Jun 26 17:39:18 2003
+++ b/drivers/pci/hotplug/acpiphp_core.c Thu Jun 26 17:39:18 2003
@@ -380,6 +380,25 @@
}
/**
+ * release_slot - free up the memory used by a slot
+ * @hotplug_slot: slot to free
+ */
+static void release_slot(struct hotplug_slot *hotplug_slot)
+{
+ struct slot *slot = get_slot(hotplug_slot, __FUNCTION__);
+
+ if (slot == NULL)
+ return;
+
+ dbg("%s - physical_slot = %s\n", __FUNCTION__, hotplug_slot->name);
+
+ kfree(slot->hotplug_slot->info);
+ kfree(slot->hotplug_slot->name);
+ kfree(slot->hotplug_slot);
+ kfree(slot);
+}
+
+/**
* init_slots - initialize 'struct slot' structures for each slot
*
*/
@@ -422,6 +441,7 @@
slot->number = i;
slot->hotplug_slot->private = slot;
+ slot->hotplug_slot->release = &release_slots;
slot->hotplug_slot->ops = &acpi_hotplug_slot_ops;
slot->acpi_slot = get_slot_from_id(i);
@@ -435,10 +455,7 @@
retval = pci_hp_register(slot->hotplug_slot);
if (retval) {
err("pci_hp_register failed with error %d\n", retval);
- kfree(slot->hotplug_slot->info);
- kfree(slot->hotplug_slot->name);
- kfree(slot->hotplug_slot);
- kfree(slot);
+ release_slot();
return retval;
}
@@ -457,13 +474,10 @@
struct slot *slot;
list_for_each_safe (tmp, n, &slot_list) {
+ /* memory will be freed in release_slot callback */
slot = list_entry(tmp, struct slot, slot_list);
list_del(&slot->slot_list);
pci_hp_deregister(slot->hotplug_slot);
- kfree(slot->hotplug_slot->info);
- kfree(slot->hotplug_slot->name);
- kfree(slot->hotplug_slot);
- kfree(slot);
}
return;
next prev parent reply other threads:[~2003-06-27 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 0:50 [BK PATCH] Yet more PCI fixes for 2.5.73 Greg KH
2003-06-27 0:51 ` [PATCH] " Greg KH
2003-06-27 0:51 ` Greg KH [this message]
2003-06-27 0:51 ` Greg KH
2003-06-27 0:51 ` Greg KH
2003-06-27 0:51 ` Greg KH
2003-06-27 0:51 ` Greg KH
2003-06-27 0:51 ` Greg KH
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=10566751041502@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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