linux-kernel - Re: [PATCH] Input: bfin_rotary - mark suspend and resume code as __maybe

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:	Fri, 6 Feb 2015 16:41:02 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Sonic Zhang <sonic.adi@...il.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Sonic Zhang <sonic.zhang@...log.com>,
	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Input: bfin_rotary - mark suspend and resume code as __maybe_unused

On Fri, Feb 6, 2015 at 10:06 AM, Sonic Zhang <sonic.adi@...il.com> wrote:
>>  static struct platform_driver bfin_rotary_device_driver = {
>>         .probe          = bfin_rotary_probe,
>>         .remove         = bfin_rotary_remove,
>>         .driver         = {
>>                 .name   = "bfin-rotary",
>
> You missed
>                    .owner  = THIS_MODULE,
> here.

That line was removed in v3.19-rc1 by commit 776bd315a7721574
("input: misc: drop owner assignment from platform_drivers").

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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/