From: Ping-Ke Shih <pkshih@realtek.com>
To: Imtiyaz Parvez <reza1234khan1234@gmail.com>,
Hungyu Lin <dennylin0707@gmail.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: allow key removal when the CAM table is full
Date: Thu, 29 Oct 2026 01:22:37 +0000 [thread overview]
Message-ID: <4f88bc4989c444cd885a4784a49a7f95@realtek.com> (raw)
In-Reply-To: <DMGRRA9L08L3.1IM2GZHXGLZQ1@gmail.com>
Imtiyaz Parvez <reza1234khan1234@gmail.com> wrote:
> Hi Hungyu,
>
> > Have you had a chance to test this patch?
>
> Yes, sorry for the delay. I tested it on my laptop.
>
> Hardware: RTL8822CE 802.11ac | kernel version: 7.2.11-arch1-1
>
> I built only the rtw88 modules from the v7.2.11 source
> tree with this patch applied, and loaded them.
>
> I used it for around 2 hours with normal browsing, suspend/resume and
> reconnecting. No new warnings or errors in dmesg.
To hit the problem this patch fixes, we need 28 pairwise entries as
Luka's mention [1]. I think it is not easy to prepare so many stations
devices.
Anyway. As your result, it proves that this patch is okay for normal use.
[1] https://lore.kernel.org/linux-wireless/334c6e785a5d242c6f168d57d042d63b777a242a@linux.dev/
next prev parent reply other threads:[~2026-10-29 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:51 Hungyu Lin
2026-10-19 19:01 ` Luka Gejak
2026-10-20 2:07 ` Ping-Ke Shih
2026-10-20 4:43 ` Luka Gejak
2026-10-20 5:29 ` Ping-Ke Shih
2026-10-20 8:28 ` Hungyu Lin
[not found] ` <CANQ=N_C3+gpQ3O=SXYpRCGTh_MC1y4TEfnxF90SWgUVF_wYPUA@mail.gmail.com>
2026-10-20 21:00 ` Hungyu Lin
2026-10-28 5:45 ` Hungyu Lin
2026-10-28 20:55 ` Imtiyaz Parvez
2026-10-29 1:22 ` Ping-Ke Shih [this message]
2026-10-28 20:56 ` Imtiyaz Parvez
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=4f88bc4989c444cd885a4784a49a7f95@realtek.com \
--to=pkshih@realtek.com \
--cc=dennylin0707@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=reza1234khan1234@gmail.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
all inboxes | Powered by JetHome®