Hi Mark,

In embedded environments the requirements are to be able to pick and chose which features one requires built into the kernel. If an embedded environment wants to supports loading modules that have been kbuilt out of tree, there is a need to enable hidden configurations for core features to provide the API surface for them to load.

Introduce CONFIG_WIRELESS_ALLCONFIG to select all wireless core features by activating all the hidden configuration options, without having to specifically select any wireless module(s).

Signed-off-by: Mark Salyzyn salyzyn@android.com Cc: kernel-team@android.com Cc: Johannes Berg johannes@sipsolutions.net Cc: "David S. Miller" davem@davemloft.net Cc: linux-wireless@vger.kernel.org Cc: netdev@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org # 4.19

---

net/wireless/Kconfig | 14 ++++++++++++++ 1 file changed, 14 insertions(+)

diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig index 67f8360dfcee..0d32350e1729 100644 --- a/net/wireless/Kconfig +++ b/net/wireless/Kconfig @@ -17,6 +17,20 @@ config WEXT_SPY config WEXT_PRIV bool

+config WIRELESS_ALLCONFIG

• bool "allconfig for wireless core"
• select WIRELESS_EXT
• select WEXT_CORE
• select WEXT_PROC
• select WEXT_SPY
• select WEXT_PRIV
• help

•  Config option used to enable all the wireless core functionality
  

•  used by modules.
  

•  If you are not building a kernel to be used for a variety of
  

•  out-of-kernel built wireless modules, say N here.
  

this looks rather legacy Wireless Extension (wext) specific. So it might be better to clearly name the option “legacy” and “wext” to not confuse anybody running an actual modern driver and userspace.

Regards

Marcel