Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
37c7e3f3
Commit
37c7e3f3
authored
20 years ago
by
Greg Kroah-Hartman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
PCI Hotplug: fix stupid directory name of "pci_hotplug_slots" to be just "slots"
parent
07c9872e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
2 deletions
+13
-2
drivers/pci/hotplug/pci_hotplug_core.c
drivers/pci/hotplug/pci_hotplug_core.c
+13
-2
No files found.
drivers/pci/hotplug/pci_hotplug_core.c
View file @
37c7e3f3
...
...
@@ -104,8 +104,19 @@ static struct kobj_type hotplug_slot_ktype = {
.
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
[]
=
{
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment