dect
/
linux-2.6
Archived
13
0
Fork 0

staging/tidspbridge: use module_platform_driver

the code under _init and _exit does platform_driver_register and
platform_driver_unregister respectively only,

so its better to use the module_platform_driver than just replicating
the module_platform_driver's implementation

Signed-off-by: Devendra Naga <develkernel412222@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Devendra Naga 2012-07-21 14:41:00 +05:45 committed by Greg Kroah-Hartman
parent 0142919c58
commit b95dd03df2
1 changed files with 1 additions and 13 deletions

View File

@ -613,16 +613,6 @@ static struct platform_driver bridge_driver = {
#endif
};
static int __init bridge_init(void)
{
return platform_driver_register(&bridge_driver);
}
static void __exit bridge_exit(void)
{
platform_driver_unregister(&bridge_driver);
}
/* To remove all process resources before removing the process from the
* process context list */
int drv_remove_all_resources(void *process_ctxt)
@ -636,6 +626,4 @@ int drv_remove_all_resources(void *process_ctxt)
return status;
}
/* Bridge driver initialization and de-initialization functions */
module_init(bridge_init);
module_exit(bridge_exit);
module_platform_driver(bridge_driver);