linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] wifi: wireless: deny wireless extensions on MLO-capable devices
Date: Thu, 17 Nov 2022 13:05:50 +0200	[thread overview]
Message-ID: <87y1s9alip.fsf@kernel.org> (raw)
In-Reply-To: <05d8f323f68412c1e0284ccf52321ab776674a59.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 17 Nov 2022 11:58:34 +0100")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Thu, 2022-11-17 at 12:51 +0200, Kalle Valo wrote:
>> Johannes Berg <johannes@sipsolutions.net> writes:
>> 
>> > From: Johannes Berg <johannes.berg@intel.com>
>> > 
>> > These are new devices that will be introduced into the market
>> 
>> s/new/Wi-Fi 7/?
>> 
>> > in 2023, with new drivers. Wireless extensions haven't been in
>> > real development since 2006. Since wireless has evolved a lot,
>> > and continues to evolve significantly with MLO, there's really
>> 
>> s/MLO/Multi-Link Operation/?
>> 
>> It would good to spell out the acronym at least once per commit log.
>
> :)
>
>> > +++ b/net/wireless/wext-core.c
>> > @@ -662,6 +662,8 @@ struct iw_statistics *get_wireless_stats(struct net_device *dev)
>> >  	    dev->ieee80211_ptr->wiphy->wext &&
>> >  	    dev->ieee80211_ptr->wiphy->wext->get_wireless_stats) {
>> >  		wireless_warn_cfg80211_wext();
>> > +		if (dev->ieee80211_ptr->wiphy->flags & WIPHY_FLAG_SUPPORTS_MLO)
>> > +			return NULL;
>> 
>> Should we have a some kind of warning in this case as well? Otherwise
>> the user has no idea why it stopped working, right?
>
> Well it's added after the warning wireless_warn_cfg80211_wext(), so it
> already prints the warning from the previous.
>
> I guess we could make an argument to the warning and modify the message
> if it's rejected?

Sorry, I was blind again :) I first read that the call to
wireless_warn_cfg80211_wext() was removed, but clearly it wasn't, and
IMHO that warning is enough. So please ignore this comment.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-11-17 11:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:42 [RFC PATCH 1/2] wifi: wireless: warn on most wireless extension usage Johannes Berg
2022-11-04 16:42 ` [RFC PATCH 2/2] wifi: wireless: deny wireless extensions on MLO-capable devices Johannes Berg
2022-11-17 10:51   ` Kalle Valo
2022-11-17 10:58     ` Johannes Berg
2022-11-17 11:05       ` Kalle Valo [this message]
2022-11-17 10:48 ` [RFC PATCH 1/2] wifi: wireless: warn on most wireless extension usage Kalle Valo
2022-11-17 10:49   ` Johannes Berg

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=87y1s9alip.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).