linux-kernel - Re: [PATCH] mmc: vt8500: Remove erroneous __exitp in wmt_mci

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

Date:	Mon, 28 Jan 2013 16:23:30 -0500
From:	Chris Ball <cjb@...top.org>
To:	Tony Prisk <linux@...sktech.co.nz>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	vt8500-wm8505-linux-kernel@...glegroups.com,
	linux-mmc@...r.kernel.org
Subject: Re: [PATCH] mmc: vt8500: Remove erroneous __exitp in wmt_mci_driver

Hi Tony,

On Sun, Jan 13 2013, Tony Prisk wrote:
> With the __devinit/__devexit attributes having been removed, this
> __exitp attribute causes an unused function warning and should be
> removed as well.
>
> Signed-off-by: Tony Prisk <linux@...sktech.co.nz>
> ---
>  drivers/mmc/host/wmt-sdmmc.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/wmt-sdmmc.c b/drivers/mmc/host/wmt-sdmmc.c
> index 154f0e8..c6d0015 100644
> --- a/drivers/mmc/host/wmt-sdmmc.c
> +++ b/drivers/mmc/host/wmt-sdmmc.c
> @@ -1012,7 +1012,7 @@ static const struct dev_pm_ops wmt_mci_pm = {
>  
>  static struct platform_driver wmt_mci_driver = {
>  	.probe = wmt_mci_probe,
> -	.remove = __exit_p(wmt_mci_remove),
> +	.remove = wmt_mci_remove,
>  	.driver = {
>  		.name = DRIVER_NAME,
>  		.owner = THIS_MODULE,

Thanks, pushed to mmc-next for 3.9.

- Chris.
-- 
Chris Ball   <cjb@...top.org>   <http://printf.net/>
One Laptop Per Child
--
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/