All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	David Miller <davem@davemloft.net>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-06-04
Date: Sun, 07 Jun 2009 17:29:43 +0200	[thread overview]
Message-ID: <1244388583.23850.87.camel@localhost.localdomain> (raw)
In-Reply-To: <4A2BD8A5.4040302@hartkopp.net>

Hi Oliver,

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

compiling RFKILL itself as a module is still working perfectly fine. It
is just the RFKILL_INPUT that can't be built as a module anymore. That
part was pointless anyway. And in the future RFKILL_INPUT will go away
and be replaced by a userspace implementation with proper support for
platform specific policies.

Regards

Marcel



WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
To: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
Cc: "John W. Linville"
	<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2009-06-04
Date: Sun, 07 Jun 2009 17:29:43 +0200	[thread overview]
Message-ID: <1244388583.23850.87.camel@localhost.localdomain> (raw)
In-Reply-To: <4A2BD8A5.4040302-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>

Hi Oliver,

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

compiling RFKILL itself as a module is still working perfectly fine. It
is just the RFKILL_INPUT that can't be built as a module anymore. That
part was pointless anyway. And in the future RFKILL_INPUT will go away
and be replaced by a userspace implementation with proper support for
platform specific policies.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-07 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 15:20 pull request: wireless-next-2.6 2009-06-04 John W. Linville
2009-06-07 10:37 ` David Miller
2009-06-07 14:18   ` Oliver Hartkopp
2009-06-07 14:58     ` John W. Linville
2009-06-07 15:04       ` Oliver Hartkopp
2009-06-07 15:04         ` Oliver Hartkopp
2009-06-07 15:11       ` Oliver Hartkopp
2009-06-07 15:11         ` Oliver Hartkopp
2009-06-07 15:26         ` John W. Linville
2009-06-07 15:29         ` Marcel Holtmann [this message]
2009-06-07 15:29           ` Marcel Holtmann
2009-06-14  8:54           ` rfkill regression in net-next-2.6 Oliver Hartkopp
2009-06-14  8:54             ` Oliver Hartkopp
2009-06-14  9:17             ` Oliver Hartkopp
2009-06-14  9:17               ` Oliver Hartkopp
2009-06-15 12:04             ` John W. Linville
2009-06-15 12:04               ` John W. Linville
2009-06-15 12:24               ` Johannes Berg
2009-06-15 12:24                 ` Johannes Berg
2009-06-15 13:20                 ` Oliver Hartkopp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1244388583.23850.87.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.