linux-kernel - Re: [PATCH RFC v3 3/3] i2c: pxa: use module_platform

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:	Thu, 23 May 2013 21:48:22 +0800
From:	Libo Chen <chenlibo.3@...il.com>
To:	wsa@...-dreams.de
CC:	Libo Chen <libo.chen@...wei.com>, guz.fnst@...fujitsu.com,
	sonic.zhang@...log.com, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC v3 3/3] i2c: pxa: use module_platform_driver() replace
 init/exit

maybe I make a mistake, please drop it.

于 2013-5-23 20:00, Libo Chen 写道:
> use module_platform_driver() macro to replace the module init/exit
> 
> Signed-off-by: Libo Chen<libo.chen@...wei.com>
> ---
>   drivers/i2c/busses/i2c-pxa.c |   10 +---------
>   1 files changed, 1 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
> index 7b10102..e9c3524 100644
> --- a/drivers/i2c/busses/i2c-pxa.c
> +++ b/drivers/i2c/busses/i2c-pxa.c
> @@ -1242,15 +1242,7 @@ static struct platform_driver i2c_pxa_driver = {
>   	.id_table	= i2c_pxa_id_table,
>   };
>   
> -static int __init i2c_adap_pxa_init(void)
> -{
> -	return platform_driver_register(&i2c_pxa_driver);
> -}
> -
> -static void __exit i2c_adap_pxa_exit(void)
> -{
> -	platform_driver_unregister(&i2c_pxa_driver);
> -}
> +module_platform_driver(i2c_pxa_driver);
>   
>   MODULE_LICENSE("GPL");
>   MODULE_ALIAS("platform:pxa2xx-i2c");

--
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/