linux-kernel - Re: [PATCH] move corgi-ssp's probe function to .devinit.text

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Jul 2009 16:44:01 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
CC:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	Eric Miao <eric.miao@...vell.com>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Paul Sokolovsky <pmiscml@...il.com>,
	Richard Purdie <rpurdie@...ys.net>,
	Liam Girdwood <liam.girdwood@...fsonmicro.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] move corgi-ssp's probe function to .devinit.text

Uwe Kleine-König wrote:
> A pointer to corgi_ssp_probe is passed to the core via
> platform_driver_register and so the function must not disappear when the
> .init sections are discarded.  Otherwise (when having HOTPLUG=y)
> unbinding and binding a device to the driver via sysfs will result in an
> oops as does a device being registered late.
> 
> An alternative to this patch is using platform_driver_probe instead of
> platform_driver_register plus removing the pointer to the probe function
> from the struct platform_driver.
> 

This corgi_ssp.c and corgi_lcd.c will be obsoleted soon, the only user
corgi_ts.c has been marked as deprecated, and will be remove once the
ssp cleanup work is done, so further fixes to these files are pointless.
--
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/