The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>, Leonard Lausen <leonard@lausen.nl>
Cc: "leonard@lausen.nl" <leonard@lausen.nl>,
	"David Härdeman" <david@hardeman.nu>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH rtw-next v3 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead
Date: Tue, 17 Nov 2026 00:54:28 +0000	[thread overview]
Message-ID: <b2ccb54c9b264722b2fac5ddbf854379@realtek.com> (raw)
In-Reply-To: <0867C5E9-DDCC-448A-A22A-9AEEFE009358@linux.dev>

Hi Luka,

Luka Gejak <luka.gejak@linux.dev> wrote:
> Hi Leonard,
> 
> On November 16, 2026 9:57:36 PM GMT+01:00, Leonard Lausen
> <leonard@lausen.nl> wrote:
> >Reduce RTL8822CS SDIO request overhead by filtering hardware-handled
> >control frames and combining adjacent TX-capacity reads.
> >
> >Changes in v3:
> >- Include monitor-filter correction in patch 1 as suggested by Luka Gejak.
> >- Cache the current FIF_CONTROL request even when changed_flags omits it.
> >- Use a shared filter writer in every chip initializer and both
> >  beamforming paths, preserving the monitor override and normal default.
> >- Keep the TX-capacity read optimization unchanged from v2.
> >
> 
> Thanks for v3. It looks good to me, so for the series,
> 
> Reviewed-by: Luka Gejak <luka.gejak@linux.dev>

Since I'm not using b4 to apply patches, could you please add your tag
to each patch? Thanks. 



      reply	other threads:[~2026-11-17  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:57 [PATCH rtw-next v3 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead Leonard Lausen
2026-11-16 20:57 ` [PATCH rtw-next v3 1/2] wifi: rtw88: 8822c: filter hardware-handled control frames on SDIO Leonard Lausen
2026-11-17  5:43   ` Luka Gejak
2026-11-17  6:59   ` Ping-Ke Shih
2026-11-16 20:57 ` [PATCH rtw-next v3 2/2] wifi: rtw88: sdio: combine free TX page register reads Leonard Lausen
2026-11-17  5:43   ` Luka Gejak
2026-11-17  7:09   ` Ping-Ke Shih
2026-11-16 21:46 ` [PATCH rtw-next v3 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead Luka Gejak
2026-11-17  0:54   ` Ping-Ke Shih [this message]

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=b2ccb54c9b264722b2fac5ddbf854379@realtek.com \
    --to=pkshih@realtek.com \
    --cc=david@hardeman.nu \
    --cc=heiko@sntech.de \
    --cc=leonard@lausen.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=shawn.lin@rock-chips.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