From: Felix Fietkau <nbd@nbd.name>
To: Shengyu Qu <wiagn233@outlook.com>,
pkshih@realtek.com, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
johannes.berg@intel.com, miriam.rachel.korenblit@intel.com,
christophe.jaillet@wanadoo.fr, greearb@candelatech.com,
howard-yh.hsu@mediatek.com, StanleyYP.Wang@mediatek.com,
deren.wu@mediatek.com, chui-hao.chiu@mediatek.com,
quic_adisi@quicinc.com, gustavoars@kernel.org,
razvan.grigore@vampirebyte.ro, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: Sujuan Chen <sujuan.chen@mediatek.com>, Bo Jiao <bo.jiao@mediatek.com>
Subject: Re: [PATCH v10 RESEND] wifi: mt76: mt7915: add wds support when wed is enabled
Date: Wed, 25 Jun 2025 12:18:07 +0200 [thread overview]
Message-ID: <26e6c7f7-a35f-4ebb-a55b-ade2ac7c20bb@nbd.name> (raw)
In-Reply-To: <TY4PR01MB1443294C4D36DF73852B4E79B9878A@TY4PR01MB14432.jpnprd01.prod.outlook.com>
On 24.06.25 16:11, Shengyu Qu wrote:
> Hi Felix,
>
> Please, tell me if this patch needs any polishing. I really don't know
> why this patch still not get merged after such a long time(and 2x
> resend), especially it already got a Reviewed-by and is a bugfix.
Hi Shengyu,
sorry it took such a long time for me to take a look at this patch.
I don't see how it can even work properly in its current form, because
of at least one bug:
When switching from non-wds to wds mode, the code calls
mt7915_mac_sta_add in order to create the new sta. However, after
changes that I made a while back, this function does not actually upload
the station to the MCU anymore, since it is called on the NOTEXIST->NONE
transition before assoc. Without corresponding ASSOC/AUTHORIZE events
(handled by mt7915_mac_sta_event), the firmware doesn't get any data for
the new wcid.
That said, I finally got around to starting to rework your patch myself.
I will let you know when I have something ready for testing, hopefully
later today.
- Felix
next prev parent reply other threads:[~2025-06-25 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 14:04 [PATCH v10 RESEND] wifi: mt76: mt7915: add wds support when wed is enabled Shengyu Qu
2025-05-18 14:41 ` Shengyu Qu
2025-05-25 13:42 ` Shengyu Qu
2025-06-24 14:11 ` Shengyu Qu
2025-06-25 10:18 ` Felix Fietkau [this message]
2025-06-25 11:00 ` Felix Fietkau
2025-06-25 17:25 ` Shengyu Qu
-- strict thread matches above, loose matches on Subject: below --
2025-04-12 9:49 Shengyu Qu
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=26e6c7f7-a35f-4ebb-a55b-ade2ac7c20bb@nbd.name \
--to=nbd@nbd.name \
--cc=StanleyYP.Wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bo.jiao@mediatek.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=chui-hao.chiu@mediatek.com \
--cc=deren.wu@mediatek.com \
--cc=greearb@candelatech.com \
--cc=gustavoars@kernel.org \
--cc=howard-yh.hsu@mediatek.com \
--cc=johannes.berg@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=pkshih@realtek.com \
--cc=quic_adisi@quicinc.com \
--cc=razvan.grigore@vampirebyte.ro \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.com \
--cc=wiagn233@outlook.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).