netdev - Re: [PATCH] RFKILL: fix input layer initialisation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080623091714.ZZRA012@mailhub.coreip.homeip.net>
Date:	Mon, 23 Jun 2008 09:22:39 -0400
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Dmitry Baryshkov <dbaryshkov@...il.com>
Cc:	netdev@...r.kernel.org, IvDoorn@...il.com
Subject: Re: [PATCH] RFKILL: fix input layer initialisation

Hi Dmitry,

On Thu, Jun 19, 2008 at 03:28:41PM +0400, Dmitry Baryshkov wrote:
> Initialise correctly last fields, so tasks can be actually executed
> 
> Also move rfkill-input initialisation to subsys level so that it's
> available before generic drivers probing occurs.
> 

Rfkill-input is an implementation of default policy of handling
wifi-related key presses, it is not mandatory and should not be
required for a driver to operate, it may even not be present in the
kernel and therefore module_init is the appropriate time for its
initialization. We don't expect user to start pushing WIFI buttons
while system just starting to boot up, do we?

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html