From: Johannes Berg <johannes@sipsolutions.net>
To: backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: [PATCH] backport: remove wext warning
Date: Fri, 16 Apr 2021 11:56:33 +0200 [thread overview]
Message-ID: <20210416115633.252b99aac931.I7a66b0233a0b6972378bb20b8d1a70b7360af932@changeid> (raw)
From: Johannes Berg <johannes.berg@intel.com>
wireless extensions are being used less, so remove the
warning about them not working - most people probably
won't ever see any failures, and even if not see the
warning.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
.../0010-add-wext-handlers-to-netdev/net_wireless_core.patch | 5 -----
1 file changed, 5 deletions(-)
diff --git a/patches/0010-add-wext-handlers-to-netdev/net_wireless_core.patch b/patches/0010-add-wext-handlers-to-netdev/net_wireless_core.patch
index 18b50f12601b..6397a04e1e40 100644
--- a/patches/0010-add-wext-handlers-to-netdev/net_wireless_core.patch
+++ b/patches/0010-add-wext-handlers-to-netdev/net_wireless_core.patch
@@ -18,11 +18,6 @@
+#ifdef CONFIG_WIRELESS_EXT
+ if (!wdev->netdev->wireless_handlers)
+ wdev->netdev->wireless_handlers = &cfg80211_wext_handler;
-+#else
-+ printk_once(KERN_WARNING "cfg80211: wext will not work because "
-+ "kernel was compiled with CONFIG_WIRELESS_EXT=n. "
-+ "Tools using wext interface, like iwconfig will "
-+ "not work.\n");
+#endif
wdev->wext.default_key = -1;
wdev->wext.default_mgmt_key = -1;
--
2.30.2
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2021-04-16 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 9:56 Johannes Berg [this message]
2021-05-04 21:35 ` [PATCH] backport: remove wext warning Hauke Mehrtens
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=20210416115633.252b99aac931.I7a66b0233a0b6972378bb20b8d1a70b7360af932@changeid \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@intel.com \
/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.