All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Brian Norris <briannorris@chromium.org>,
	Matthew Wang <matthewmwang@google.com>
Cc: linux-wireless@vger.kernel.org, Kirtika Ruchandani <kirtika@google.com>
Subject: Re: Flag for detecting 802.11r Fast BSS Transition support
Date: Wed, 21 Aug 2019 10:03:34 +0200	[thread overview]
Message-ID: <ce69a3dfbdeb092653212475ec849770cf9240ba.camel@sipsolutions.net> (raw)
In-Reply-To: <20190403210200.GA93453@google.com> (sfid-20190403_230207_629987_2069AD98)

On Wed, 2019-04-03 at 14:02 -0700, Brian Norris wrote:
> + Johannes
> 
> On Thu, Oct 04, 2018 at 12:06:50PM -0700, Matthew Wang wrote:
> > Hi,
> > 
> > I'm wondering if there is a flag for detecting firmware/driver support
> > for FT. It seems like checking for SME support is a pretty good proxy
> > for this, but there is a non-mac80211 driver that can do FT as well
> > (ath/wil6210). It would be great if anyone knows of a feature flag
> > specifically for FT.
> 
> I chatted with Johannes, and he agreed that there was no such flag
> today. It also sounded like he was open to adding one, even if it's
> several years too late.

Yeah, well, hindsight is 20/20. I think I've tried to do better in
reviews wrt. feature flags or some other way of discovering it, but I
guess it's never going to be perfect.

Can you submit a patch?

johannes



      parent reply	other threads:[~2019-08-21  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 19:06 Flag for detecting 802.11r Fast BSS Transition support Matthew Wang
2019-04-03 21:02 ` Brian Norris
2019-04-08 19:52   ` Johannes Berg
2019-08-08 17:15     ` Brian Norris
2019-08-16 18:54       ` Marcel Holtmann
2019-08-16 20:29         ` Brian Norris
2019-08-17 13:40           ` Marcel Holtmann
2019-08-21 16:54             ` Brian Norris
2019-08-21 16:59               ` Marcel Holtmann
2019-08-21  8:03   ` Johannes Berg [this message]

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=ce69a3dfbdeb092653212475ec849770cf9240ba.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=briannorris@chromium.org \
    --cc=kirtika@google.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthewmwang@google.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.