From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@adapt-ip.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 3/7] mac80211: handle channel frequency offset
Date: Wed, 01 Apr 2020 08:59:18 +0200 [thread overview]
Message-ID: <7fc6331597f53f5d100f3aa7e29434c20cf6fe90.camel@sipsolutions.net> (raw)
In-Reply-To: <20200401062150.3324-4-thomas@adapt-ip.com>
On Tue, 2020-03-31 at 23:21 -0700, Thomas Pedersen wrote:
> ie. ignore
> for mesh, ibss, HT/VHT specific stuff, TDLS, etc.
This makes sense, but I don't see that you prevent using mesh, ibss and
perhaps TDLS on s1g channels?
Or do we not expect drivers/devices that support this, as well as S1G
channels?
johannes
next prev parent reply other threads:[~2020-04-01 6:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 6:21 [RFC 0/7] add a KHz component to wireless channels Thomas Pedersen
2020-04-01 6:21 ` [RFC 1/7] ieee80211: share 802.11 unit conversion helpers Thomas Pedersen
2020-04-01 6:21 ` [RFC 2/7] cfg80211: express channels with a KHz component Thomas Pedersen
2020-04-01 6:54 ` Johannes Berg
2020-04-01 17:30 ` Thomas Pedersen
2020-04-01 17:53 ` Johannes Berg
2020-04-01 21:32 ` Thomas Pedersen
2020-04-01 6:21 ` [RFC 3/7] mac80211: handle channel frequency offset Thomas Pedersen
2020-04-01 6:59 ` Johannes Berg [this message]
2020-04-01 17:39 ` Thomas Pedersen
2020-04-01 17:53 ` Johannes Berg
2020-04-01 6:21 ` [RFC 4/7] mac80211: add freq_offset to RX status Thomas Pedersen
2020-04-01 7:08 ` Johannes Berg
2020-04-01 17:58 ` Thomas Pedersen
2020-04-01 6:21 ` [RFC 5/7] cfg80211: report frequency in KHz for management RX Thomas Pedersen
2020-04-01 6:21 ` [RFC 6/7] nl80211: add KHz frequency offset for most wifi commands Thomas Pedersen
2020-04-01 7:10 ` Johannes Berg
2020-04-01 18:15 ` Thomas Pedersen
2020-04-01 7:12 ` Johannes Berg
2020-04-01 6:21 ` [RFC 7/7] nl80211: accept scan frequencies in KHz Thomas Pedersen
2020-04-01 7:15 ` [RFC 0/7] add a KHz component to wireless channels Johannes Berg
2020-04-01 18:26 ` Thomas Pedersen
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=7fc6331597f53f5d100f3aa7e29434c20cf6fe90.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@adapt-ip.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 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).