From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Hotplug fixes for 2.6.4-rc1
Date: Tue, 2 Mar 2004 20:21:45 -0800 [thread overview]
Message-ID: <1078287705197@kroah.com> (raw)
In-Reply-To: <10782877051959@kroah.com>
ChangeSet 1.1622, 2004/03/01 16:18:12-08:00, greg@kroah.com
PCI Hotplug: fix stupid directory name of "pci_hotplug_slots" to be just "slots"
drivers/pci/hotplug/pci_hotplug_core.c | 15 +++++++++++++--
1 files changed, 13 insertions(+), 2 deletions(-)
diff -Nru a/drivers/pci/hotplug/pci_hotplug_core.c b/drivers/pci/hotplug/pci_hotplug_core.c
--- a/drivers/pci/hotplug/pci_hotplug_core.c Tue Mar 2 19:42:42 2004
+++ b/drivers/pci/hotplug/pci_hotplug_core.c Tue Mar 2 19:42:42 2004
@@ -104,8 +104,19 @@
.release = &hotplug_slot_release,
};
-decl_subsys(pci_hotplug_slots, &hotplug_slot_ktype, NULL);
-
+/*
+ * We create a struct subsystem on our own and not use decl_subsys so
+ * we can have a sane name "slots" in sysfs, yet still keep a good
+ * global variable name "pci_hotplug_slots_subsys.
+ * If the decl_subsys() #define ever changes, this declaration will
+ * need to be update to make sure everything is initialized properly.
+ */
+struct subsystem pci_hotplug_slots_subsys = {
+ .kset = {
+ .kobj = { .name = "slots" },
+ .ktype = &hotplug_slot_ktype,
+ }
+};
/* these strings match up with the values in pci_bus_speed */
static char *pci_bus_speed_strings[] = {
next prev parent reply other threads:[~2004-03-03 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 4:20 [BK PATCH] PCI Hotplug fixes for 2.6.4-rc1 Greg KH
2004-03-03 4:21 ` [PATCH] " Greg KH
2004-03-03 4:21 ` Greg KH [this message]
2004-03-03 4:21 ` Greg KH
2004-03-03 4:21 ` Greg KH
2004-03-03 4:21 ` Greg KH
2004-03-04 6:17 ` Ingo Oeser
2004-03-04 18:27 ` 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=1078287705197@kroah.com \
--to=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 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.