linux-kernel - Re: [PATCH 2/4] wimax: fix kconfig interactions with rfkill and input layers

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: <20090108.110743.163052787.davem@davemloft.net>
Date:	Thu, 08 Jan 2009 11:07:43 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	inaky@...ux.intel.com
Cc:	netdev@...r.kernel.org, wimax@...uxwimax.org, greg@...ah.com,
	randy.dunlap@...cle.com, sfr@...b.auug.org.au,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-wimax@...el.com
Subject: Re: [PATCH 2/4] wimax: fix kconfig interactions with rfkill and
 input layers

From: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
Date: Wed,  7 Jan 2009 11:22:20 -0800

> WiMAX can work without RFKILL, but it was missing a check to make sure
> RFKILL is not being made a module with wimax compiled into the
> kernel. This caused failed builds in s390, where CONFIG_INPUT is
> always off.
> 
> When RFKILL is enabled, the code uses the input layer to report
> hardware switch changes; thus, if RFKILL is enabled, INPUT has to be
> too. It also needs to display some message when INPUT is disabled that
> explains why WiMAX is not selectable.
> 
> (issues found by Randy Dunlap in the linux-next tree).
> 
> Signed-off-by: Inaky Perez-Gonzalez <inaky@...ux.intel.com>

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