linux-kernel - Re: kobject link failure

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.64.0707201756290.31013@fbirervta.pbzchgretzou.qr>
Date:	Fri, 20 Jul 2007 18:02:25 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Greg KH <gregkh@...e.de>
cc:	Cornelia Huck <cornelia.huck@...ibm.com>,
	Gabriel C <nix.or.die@...glemail.com>,
	Robert Schwebel <r.schwebel@...gutronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	kay.sievers@...y.org
Subject: Re: kobject link failure


On Jul 20 2007 08:06, Greg KH wrote:
>> Leaving kobject_actions[] in kobject_uevent.c, but putting it outside
>> the #ifdef looks indeed like the best solution to me. This way, we
>> avoid adding #ifdef CONFIG_HOTPLUG into core.c, when all other
>> functions called do not need such a thing.
>
>Yeah, this is much nicer and smaller, thanks.  I'll throw away my patch
>and use this one instead.
>
>Can someone verify that it works properly for them please?

Works-For-Me™: Jan Engelhardt <jengelh@....de>


	Jan
--