From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@adapt-ip.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 5/9] cfg80211: report frequency in KHz for management RX
Date: Fri, 24 Apr 2020 12:11:21 +0200 [thread overview]
Message-ID: <d720e6c495aeb8cb6d17cf44b8c15d96de48b61d.camel@sipsolutions.net> (raw)
In-Reply-To: <20200402011810.22947-6-thomas@adapt-ip.com>
On Wed, 2020-04-01 at 18:18 -0700, Thomas Pedersen wrote:
> Expect and convert drivers to report the RX frequency to
> cfg80211_rx_mgmt() and cfg80211_report_obss_beacon() in
> KHz
I would prefer to have some inlines for this, and add
cfg80211_rx_mgmt_khz() or something.
You've had to change a lot of drivers, but I got conflicts, and you also
missed some (which may have added the code since you created the
patches, or you prepared against mac80211-next and that code was waiting
elsewhere, etc.)
I've applied patches 1-4, but please respin the rest.
johannes
next prev parent reply other threads:[~2020-04-24 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 1:18 [PATCH 0/9] initial support for S1G channels Thomas Pedersen
2020-04-02 1:18 ` [PATCH 1/9] ieee80211: share 802.11 unit conversion helpers Thomas Pedersen
2020-04-02 1:18 ` [PATCH 2/9] cfg80211: express channels with a KHz component Thomas Pedersen
2020-04-02 1:18 ` [PATCH 3/9] mac80211: handle channel frequency offset Thomas Pedersen
2020-04-02 1:18 ` [PATCH 4/9] mac80211: add freq_offset to RX status Thomas Pedersen
2020-04-02 1:18 ` [PATCH 5/9] cfg80211: report frequency in KHz for management RX Thomas Pedersen
2020-04-24 10:11 ` Johannes Berg [this message]
2020-04-02 1:18 ` [PATCH 6/9] nl80211: add KHz frequency offset for most wifi commands Thomas Pedersen
2020-04-02 1:18 ` [PATCH 7/9] nl80211: accept scan frequencies in KHz Thomas Pedersen
2020-04-02 1:18 ` [PATCH 8/9] ieee80211: S1G defines Thomas Pedersen
2020-04-02 1:18 ` [PATCH 9/9] nl80211: S1G band and channel definitions 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=d720e6c495aeb8cb6d17cf44b8c15d96de48b61d.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 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.