linux-kernel - Re: [PATCH 05/28] cpufreq: drop owner assignment from 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:	Mon, 22 Dec 2014 07:14:56 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 05/28] cpufreq: drop owner assignment from platform_drivers

On 22 December 2014 at 02:44, Wolfram Sang <wsa@...-dreams.de> wrote:
> This platform_driver does not need to set an owner, it will be populated by the
> driver core.
>
> Signed-off-by: Wolfram Sang <wsa@...-dreams.de>
> ---
> Generated with coccinelle. SmPL file is in the introductory msg. The big
> cleanup was pulled in this merge window. This series catches the bits fallen
> through. The patches shall go in via the subsystem trees.
>
>  drivers/cpufreq/ls1x-cpufreq.c | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/drivers/cpufreq/ls1x-cpufreq.c b/drivers/cpufreq/ls1x-cpufreq.c
> index 25fbd6a1374f..f0913eee2f50 100644
> --- a/drivers/cpufreq/ls1x-cpufreq.c
> +++ b/drivers/cpufreq/ls1x-cpufreq.c
> @@ -210,7 +210,6 @@ out:
>  static struct platform_driver ls1x_cpufreq_platdrv = {
>         .driver = {
>                 .name   = "ls1x-cpufreq",
> -               .owner  = THIS_MODULE,
>         },
>         .probe          = ls1x_cpufreq_probe,
>         .remove         = ls1x_cpufreq_remove,

Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
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/