linux-kernel - Re: [PATCH] update sysfs kset initialisation in PPC64 DLPAR IO driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070511071606.GB1211@suse.de>
Date:	Fri, 11 May 2007 00:16:06 -0700
From:	Greg KH <gregkh@...e.de>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	paulus@...ba.org, Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org
Subject: Re: [PATCH] update sysfs kset initialisation in PPC64 DLPAR IO
	driver

On Thu, May 10, 2007 at 04:54:41PM +0100, Andy Whitcroft wrote:
> Greg KH wrote:
> > On Thu, May 10, 2007 at 03:00:50PM +0100, Andy Whitcroft wrote:
> >> Move the rpadlpar device from "struct subsystem" to "struct kset"
> >> following the changes in sysfs.
> >>
> >> Signed-off-by: Andy Whitcroft <apw@...dowen.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.
> > 
> > As per the discussion on the pci hotplug list, no, this doesn't seem to
> > fix the problem.  The developers there are looking into it.  If you can
> > test out patches for this, I'm sure the people there would appreciate
> > the help.
> 
> Sure anything they have for testing, send them to me ...

They have the same patch that you made (I made it), yet they reported
that it didn't work properly for them.

Can you test your patch out on "real" hardware?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/