mtd: nand: register orion_nand using platform_driver_probe()

orion_nand_probe lives in .init.text, so using platform_driver_register to
register it is wrong because binding a device after the init memory is
discarded (e.g. via sysfs) results in an oops.

As requested by Nicolas Pitre platform_driver_probe is used instead of
moving the probe function to .devinit.text as proposed initially. This
saves some memory, but devices registered after the driver is probed are
not bound (probably there are none) and binding via sysfs isn't possible.

Signed-off-by: Uwe Kleine-König <[e-mail]>
Cc: Lennert Buytenhek <[e-mail]>
Cc: Saeed Bishara <[e-mail]>
Cc: Joern Engel <[e-mail]>
Acked-by: Nicolas Pitre <[e-mail]>
Cc: Greg Kroah-Hartman <[e-mail]>
Signed-off-by: Andrew Morton <[e-mail]>
Signed-off-by: David Woodhouse <[e-mail]>

drivers/mtd/nand/orion_nand.c

···
 }
 
 static struct platform_driver orion_nand_driver = {
-	.probe		= orion_nand_probe,
 	.remove		= __devexit_p(orion_nand_remove),
 	.driver		= {
 		.name	= "orion_nand",
···
 
 static int __init orion_nand_init(void)
 {
-	return platform_driver_register(&orion_nand_driver);
+	return platform_driver_probe(&orion_nand_driver, orion_nand_probe);
 }
 
 static void __exit orion_nand_exit(void)