tree 28871ec8da0830362f045906fb2b97722cb6837f
parent abbf268ae8f51e19779cdf3f5fbb8144f1a5fbc3
author Russell King <rmk@dyn-67.arm.linux.org.uk> 1131225759 +0000
committer Russell King <rmk+kernel@arm.linux.org.uk> 1131225759 +0000

[DRIVER MODEL] Fix sgivwfb

Statically allocated devices in module data is a potential cause
of oopsen.  The device may be in use by a userspace process, which
will keep a reference to the device.  If the module is unloaded,
the module data will be freed.  Subsequent use of the platform
device will cause a kernel oops.

Use generic platform device allocation/release code in modules.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>