From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-2023-12-19
Date: Tue, 19 Dec 2023 23:32:14 +0100 [thread overview]
Message-ID: <20231219223233.189152-3-johannes@sipsolutions.net> (raw)
Hi,
Here are a couple of more fixes, the most important
one really being the iwlwifi rfkill fix.
Please pull and let us know if there's any problem.
Thanks,
johannes
The following changes since commit 3c2a8ebe3fe66a5f77d4c164a0bea8e2ff37b455:
wifi: cfg80211: fix certs build to not depend on file order (2023-12-14 09:11:51 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git tags/wireless-2023-12-19
for you to fetch changes up to 0a3d898ee9a8303d5b3982b97ef0703919c3ea76:
wifi: mac80211: add/remove driver debugfs entries as appropriate (2023-12-19 13:08:00 +0100)
----------------------------------------------------------------
Just a couple of things:
* debugfs fixes
* rfkill fix in iwlwifi
* remove mostly-not-working list
----------------------------------------------------------------
Benjamin Berg (2):
wifi: mac80211: do not re-add debugfs entries during resume
wifi: mac80211: add/remove driver debugfs entries as appropriate
Johannes Berg (1):
wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ
Lukas Bulwahn (1):
MAINTAINERS: wifi: brcm80211: remove non-existing SHA-cyfmac-dev-list@infineon.com
MAINTAINERS | 1 -
drivers/net/wireless/intel/iwlwifi/pcie/internal.h | 4 ++--
drivers/net/wireless/intel/iwlwifi/pcie/rx.c | 8 ++++----
drivers/net/wireless/intel/iwlwifi/pcie/trans.c | 17 +++++++++--------
net/mac80211/debugfs_netdev.c | 9 ++++++---
net/mac80211/driver-ops.c | 14 +++++++++-----
6 files changed, 30 insertions(+), 23 deletions(-)
next reply other threads:[~2023-12-19 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 22:32 Johannes Berg [this message]
2023-12-27 13:10 ` pull-request: wireless-2023-12-19 patchwork-bot+netdevbpf
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=20231219223233.189152-3-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 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.