From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Felix Fietkau <nbd@nbd.name>, Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sujuan Chen <sujuan.chen@mediatek.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Daniel Pawlik <pawlik.dan@gmail.com>,
Matteo Croce <teknoraver@meta.com>,
Peter Chiu <chui-hao.chiu@mediatek.com>
Subject: [PATCH mt76 0/2] wifi: mt76: Some WED fixes
Date: Wed, 08 Oct 2025 12:41:47 +0200 [thread overview]
Message-ID: <20251008-wed-fixes-v1-0-8f7678583385@kernel.org> (raw)
- use GFP_DMA32 for page_pool buffer allocation
- fix wed crash on 6GHz band
---
Lorenzo Bianconi (1):
wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks
Peter Chiu (1):
wifi: mt76: use GFP_DMA32 for page_pool buffer allocation
drivers/net/wireless/mediatek/mt76/mt76.h | 12 +++++++++++-
drivers/net/wireless/mediatek/mt76/mt7996/mmio.c | 1 +
drivers/net/wireless/mediatek/mt76/wed.c | 10 +++++-----
include/linux/soc/mediatek/mtk_wed.h | 1 +
4 files changed, 18 insertions(+), 6 deletions(-)
---
base-commit: f4c70f6e7bdbffce882bed0fb8c78d135458a029
change-id: 20251007-wed-fixes-f468722e2155
Best regards,
--
Lorenzo Bianconi <lorenzo@kernel.org>
next reply other threads:[~2025-10-08 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 10:41 Lorenzo Bianconi [this message]
2025-10-08 10:41 ` [PATCH mt76 1/2] wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks Lorenzo Bianconi
2025-10-08 10:41 ` [PATCH mt76 2/2] wifi: mt76: use GFP_DMA32 for page_pool buffer allocation Lorenzo Bianconi
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=20251008-wed-fixes-v1-0-8f7678583385@kernel.org \
--to=lorenzo@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chui-hao.chiu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=pawlik.dan@gmail.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.com \
--cc=teknoraver@meta.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 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).