netdev - Re: pull request: wireless-next-2.6 2009-06-04

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:	Sun, 07 Jun 2009 17:11:33 +0200
From:	Oliver Hartkopp <socketcan@...tkopp.net>
To:	"John W. Linville" <linville@...driver.com>
CC:	David Miller <davem@...emloft.net>, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-06-04

John W. Linville wrote:
> On Sun, Jun 07, 2009 at 04:18:41PM +0200, Oliver Hartkopp wrote:
>> David Miller wrote:
>>> From: "John W. Linville" <linville@...driver.com>
>>> Date: Thu, 4 Jun 2009 11:20:11 -0400
>>>
>>>> Hopefully this is (almost?) the last wireless pull request for
>>>> non-bugfix patches intended for 2.6.31...
>>>>
>> (..)
>>
>>>> Please let me know if there are problems!
>>> Pulled into net-next-2.6 and I'll push it back out to kernel.org
>>> after some build testing.
>> Hi John,
>>
>> after pulling the latest net-next-2.6 i got this warning which is probably
>> caused by CONFIG_RFKILL=m in my config:
>>
>> hartko@...gwolkf320:~/net-next-2.6$ make oldconfig
>> scripts/kconfig/conf -o arch/x86/Kconfig
>> .config:614:warning: symbol value 'm' invalid for RFKILL_INPUT
> 
> That functionality is no longer available as a module.  If you need
> it, then select Y.

Just some additional nitpicking:

You should update net/rfkill/Kconfig as it still allows a tristate selection
for RFKILL and the comment "To compile this driver as a module ..." should be
removed also.

Regards,
Oliver

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