From: Kalle Valo <kvalo@codeaurora.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-drivers-next-2021-10-25
Date: Mon, 25 Oct 2021 08:44:10 +0000 (UTC) [thread overview]
Message-ID: <20211025084410.BB75DC4360D@smtp.codeaurora.org> (raw)
Hi,
here's a pull request to net-next tree, more info below. Please let me know if
there are any problems.
Kalle
The following changes since commit 47b068247aa7d76bb7abea796b72e18a4c6e35c3:
net: liquidio: Make use of the helper macro kthread_run() (2021-10-22 11:10:10 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git tags/wireless-drivers-next-2021-10-25
for you to fetch changes up to 753453afacc0243bd45de45e34218a8d17493e8f:
mt76: mt7615: mt7622: fix ibss and meshpoint (2021-10-23 10:29:39 +0300)
----------------------------------------------------------------
wireless-drivers-next patches for v5.16
Third set of patches for v5.16. This time we have a small one to
quickly fix two mt76 build failures I had missed in my previous pull
request.
Major changes:
mt76
* fix linking when CONFIG_MMC is disabled
* fix dev_err() format warning
* mt7615: mt7622: fix ibss and meshpoint
----------------------------------------------------------------
Lorenzo Bianconi (1):
mt76: mt7921: fix mt7921s Kconfig
Nick Hainke (1):
mt76: mt7615: mt7622: fix ibss and meshpoint
Randy Dunlap (1):
mt76: mt7921: fix Wformat build warning
drivers/net/wireless/mediatek/mt76/mt7615/main.c | 4 ++--
drivers/net/wireless/mediatek/mt76/mt7921/Kconfig | 1 +
drivers/net/wireless/mediatek/mt76/mt7921/main.c | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
next reply other threads:[~2021-10-25 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 8:44 Kalle Valo [this message]
2021-10-25 13:20 ` pull-request: wireless-drivers-next-2021-10-25 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=20211025084410.BB75DC4360D@smtp.codeaurora.org \
--to=kvalo@codeaurora.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 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.