linux-kernel - Re: [PATCH] power: max77693: fix platform_no_drv

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]

Message-id: <1421827138.4420.3.camel@AMDC1943>
Date:	Wed, 21 Jan 2015 08:58:58 +0100
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	kbuild test robot <fengguang.wu@...el.com>
Cc:	kbuild-all@...org, Sebastian Reichel <sre@...nel.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] power: max77693: fix platform_no_drv_owner.cocci warnings

On śro, 2015-01-21 at 12:11 +0800, kbuild test robot wrote:
> drivers/power/max77693_charger.c:747:3-8: No need to set .owner here. The core will do it.
> 
>  Remove .owner field if calls are used which set it automatically
> 
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
> 
> CC: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@...el.com>
> ---
> 
>  max77693_charger.c |    1 -
>  1 file changed, 1 deletion(-)

Reviewed-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>


> 
> --- a/drivers/power/max77693_charger.c
> +++ b/drivers/power/max77693_charger.c
> @@ -744,7 +744,6 @@ MODULE_DEVICE_TABLE(platform, max77693_c
>  
>  static struct platform_driver max77693_charger_driver = {
>  	.driver = {
> -		.owner	= THIS_MODULE,
>  		.name	= "max77693-charger",
>  	},
>  	.probe		= max77693_charger_probe,

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