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

["John W. Linville" <linville@tuxdriver.com>]

On Sun, Jun 07, 2009 at 05:11:33PM +0200, Oliver Hartkopp wrote:
> 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@tuxdriver.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@vwagwolkf320:~/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.

RFKILL and RFKILL_INPUT are different things... :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.