From: Ping-Ke Shih <pkshih@realtek.com>
To: Ping-Ke Shih <pkshih@realtek.com>, <linux-wireless@vger.kernel.org>
Cc: <kevin_yang@realtek.com>
Subject: Re: [PATCH 1/4] wifi: rtw89: ser: avoid multiple deinit on same CAM
Date: Tue, 14 May 2024 09:37:12 +0800 [thread overview]
Message-ID: <548799df-8652-44ca-ac96-183d5f90bd90@RTEXMBS04.realtek.com.tw> (raw)
In-Reply-To: <20240509090646.35304-2-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> We did deinit CAM in STA iteration in VIF loop. But, the STA iteration
> missed to restrict the target VIF. So, if there are multiple VIFs, we
> would deinit a CAM multiple times. Now, fix it.
>
> Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
4 patch(es) applied to rtw-next branch of rtw.git, thanks.
cea406658830 wifi: rtw89: ser: avoid multiple deinit on same CAM
0448c65af921 wifi: rtw89: cam: tweak relation between sec CAM and addr CAM
e9f1a901c9cc wifi: rtw89: switch to register vif_cfg_changed and link_info_changed
578bdd984f45 wifi: rtw89: support mac_id number according to chip
---
https://github.com/pkshih/rtw.git
next prev parent reply other threads:[~2024-05-14 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:06 [PATCH 0/4] wifi: rtw89: adjust security CAM, mac80211_ops and mac_id for coming MLO Ping-Ke Shih
2024-05-09 9:06 ` [PATCH 1/4] wifi: rtw89: ser: avoid multiple deinit on same CAM Ping-Ke Shih
2024-05-14 1:37 ` Ping-Ke Shih [this message]
2024-05-09 9:06 ` [PATCH 2/4] wifi: rtw89: cam: tweak relation between sec CAM and addr CAM Ping-Ke Shih
2024-05-09 9:06 ` [PATCH 3/4] wifi: rtw89: switch to register vif_cfg_changed and link_info_changed Ping-Ke Shih
2024-05-09 9:06 ` [PATCH 4/4] wifi: rtw89: support mac_id number according to chip Ping-Ke Shih
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=548799df-8652-44ca-ac96-183d5f90bd90@RTEXMBS04.realtek.com.tw \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@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 read-only IMAP folder(s) and NNTP newsgroup(s).