From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: mac80211 2021-01-18.2
Date: Mon, 18 Jan 2021 21:47:49 +0100 [thread overview]
Message-ID: <20210118204750.7243-1-johannes@sipsolutions.net> (raw)
Hi,
New try, dropped the 160 MHz CSA patch for now that has the sparse
issue since people are waiting for the kernel-doc fixes.
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit 220efcf9caf755bdf92892afd37484cb6859e0d2:
Merge tag 'mlx5-fixes-2021-01-07' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux (2021-01-07 19:13:30 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-net-2021-01-18.2
for you to fetch changes up to c13cf5c159660451c8fbdc37efb998b198e1d305:
mac80211: check if atf has been disabled in __ieee80211_schedule_txq (2021-01-14 22:27:38 +0100)
----------------------------------------------------------------
Various fixes:
* kernel-doc parsing fixes
* incorrect debugfs string checks
* locking fix in regulatory
* some encryption-related fixes
----------------------------------------------------------------
Felix Fietkau (3):
mac80211: fix fast-rx encryption check
mac80211: fix encryption key selection for 802.3 xmit
mac80211: do not drop tx nulldata packets on encrypted links
Ilan Peer (1):
cfg80211: Save the regulatory domain with a lock
Johannes Berg (1):
cfg80211/mac80211: fix kernel-doc for SAR APIs
Lorenzo Bianconi (1):
mac80211: check if atf has been disabled in __ieee80211_schedule_txq
Mauro Carvalho Chehab (1):
cfg80211: fix a kerneldoc markup
Shayne Chen (1):
mac80211: fix incorrect strlen of .write in debugfs
include/net/cfg80211.h | 5 ++++-
include/net/mac80211.h | 1 +
net/mac80211/debugfs.c | 44 ++++++++++++++++++++------------------------
net/mac80211/rx.c | 2 ++
net/mac80211/tx.c | 31 +++++++++++++++++--------------
net/wireless/reg.c | 11 ++++++++++-
6 files changed, 54 insertions(+), 40 deletions(-)
next reply other threads:[~2021-01-18 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 20:47 Johannes Berg [this message]
2021-01-18 22:50 ` pull-request: mac80211 2021-01-18.2 patchwork-bot+netdevbpf
2021-01-20 17:59 ` Johannes Berg
2021-01-20 20:37 ` Jakub Kicinski
2021-01-20 20:39 ` Johannes Berg
2021-01-23 21:31 ` Hans de Goede
2021-01-23 22:15 ` Johannes Berg
2021-01-24 9:12 ` Peer, Ilan
2021-01-24 10:54 ` Hans de Goede
2021-01-24 13:03 ` Peer, Ilan
2021-01-25 9:47 ` Johannes Berg
2021-01-25 11:18 ` Hans de Goede
2021-01-25 12:40 ` Johannes Berg
2021-01-25 12:59 ` Hans de Goede
2021-01-25 13:03 ` 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=20210118204750.7243-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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