From: Andy Whitcroft <apw@shadowen•org>
To: gregkh@suse•de
Cc: Andrew Morton <akpm@osdl•org>,
linux-kernel@vger•kernel.org, linuxppc-dev@ozlabs•org,
paulus@samba•org, Linus Torvalds <torvalds@linux-foundation•org>
Subject: [PATCH] update sysfs kset initialisation in PPC64 DLPAR IO driver
Date: Thu, 10 May 2007 15:00:50 +0100 [thread overview]
Message-ID: <2c705c055fcd12202673ee8a3056153b@pinky> (raw)
In-Reply-To: 464322F3.3010808@shadowen.org
Move the rpadlpar device from "struct subsystem" to "struct kset"
following the changes in sysfs.
Signed-off-by: Andy Whitcroft <apw@shadowen•org>
---
Ok, this patch seems to sort out the compile problem
here and indeed boots and runs kernbench. Perhaps
you could confirm this is sufficient.
diff --git a/drivers/pci/hotplug/rpadlpar_sysfs.c b/drivers/pci/hotplug/rpadlpar_sysfs.c
index 6c5be3f..ed4de59 100644
--- a/drivers/pci/hotplug/rpadlpar_sysfs.c
+++ b/drivers/pci/hotplug/rpadlpar_sysfs.c
@@ -129,13 +129,13 @@ struct kobj_type ktype_dlpar_io = {
};
struct kset dlpar_io_kset = {
- .subsys = &pci_hotplug_slots_subsys,
.kobj = {.name = DLPAR_KOBJ_NAME, .ktype=&ktype_dlpar_io,},
.ktype = &ktype_dlpar_io,
};
int dlpar_sysfs_init(void)
{
+ kobj_set_kset_s(&dlpar_io_kset, pci_hotplug_slots_subsys);
if (kset_register(&dlpar_io_kset)) {
printk(KERN_ERR "rpadlpar_io: cannot register kset for %s\n",
dlpar_io_kset.kobj.name);
next prev parent reply other threads:[~2007-05-10 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 13:49 2.6.21-git5 -- powerpc link failure Andy Whitcroft
2007-05-10 14:00 ` Andy Whitcroft [this message]
2007-05-10 14:12 ` [PATCH] update sysfs kset initialisation in PPC64 DLPAR IO driver Greg KH
2007-05-10 15:54 ` Andy Whitcroft
2007-05-11 7:16 ` Greg KH
2007-05-11 7:58 ` Michael Ellerman
2007-05-11 10:40 ` Andy Whitcroft
2007-05-12 2:17 ` Michael Ellerman
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=2c705c055fcd12202673ee8a3056153b@pinky \
--to=apw@shadowen$(echo .)org \
--cc=akpm@osdl$(echo .)org \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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