From: Kalle Valo <kvalo@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-2023-02-27
Date: Mon, 27 Feb 2023 13:10:53 +0000 (UTC) [thread overview]
Message-ID: <20230227131053.BD779C433D2@smtp.kernel.org> (raw)
Hi,
here's a pull request to net tree, more info below. Please let me know if there
are any problems.
Kalle
The following changes since commit 5b7c4cabbb65f5c469464da6c5f614cbd7f730f2:
Merge tag 'net-next-6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next (2023-02-21 18:24:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git tags/wireless-2023-02-27
for you to fetch changes up to 52fd90638a7269be2a6f6cf1e4dea6724f8e13b6:
wifi: wext: warn about usage only once (2023-02-26 19:53:35 +0200)
----------------------------------------------------------------
wireless fixes for v6.3
First set of fixes for v6.3. We have only three oneliners. The most
important one is the patch reducing warnings about the Wireless
Extensions usage, reported by Linus.
----------------------------------------------------------------
Johannes Berg (1):
wifi: wext: warn about usage only once
Len Brown (1):
wifi: ath11k: allow system suspend to survive ath11k
Lorenzo Bianconi (1):
wifi: mt76: usb: fix use-after-free in mt76u_free_rx_queue
drivers/net/wireless/ath/ath11k/pci.c | 2 +-
drivers/net/wireless/mediatek/mt76/usb.c | 1 +
net/wireless/wext-core.c | 4 ++--
3 files changed, 4 insertions(+), 3 deletions(-)
next reply other threads:[~2023-02-27 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 13:10 Kalle Valo [this message]
2023-02-27 21:16 ` pull-request: wireless-2023-02-27 Jakub Kicinski
2023-02-28 0:46 ` 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=20230227131053.BD779C433D2@smtp.kernel.org \
--to=kvalo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).