From: Ping-Ke Shih <pkshih@realtek.com>
To: Ho Jie Feng <hjf3108@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH rtw-next 3/5] wifi: rtlwifi: usb: unify the RX code path
Date: Mon, 9 Nov 2026 00:40:19 +0000 [thread overview]
Message-ID: <5371f205934a4dfd86cae13ffeebcf7c@realtek.com> (raw)
In-Reply-To: <20261103095256.949327-4-hjf3108@gmail.com>
Ho Jie Feng <hjf3108@gmail.com> wrote:
> _rtl_usb_rx_process_agg is a copy of _rtl_usb_rx_process_noagg
> except without the tail end. The noagg function can be used for
> aggregated frames, so drop it and rename _rtl_usb_rx_process_noagg
> to _rtl_usb_rx_process to unify the code path.
>
> Signed-off-by: Ho Jie Feng <hjf3108@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2026-11-09 0:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:52 [PATCH rtw-next 0/5] wifi: rtlwifi: rtl8192du fixes and additional support Ho Jie Feng
2026-11-03 9:52 ` [PATCH rtw-next 1/5] wifi: rtlwifi: rc: start no BA session for QoS null frames Ho Jie Feng
2026-11-08 4:08 ` Ping-Ke Shih
2026-11-08 18:11 ` Jie Feng
2026-11-09 2:49 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 2/5] wifi: rtlwifi: rtl8192d: report no signal for frames without PHY status Ho Jie Feng
2026-11-08 4:13 ` Ping-Ke Shih
2026-11-08 18:12 ` Jie Feng
2026-11-09 2:51 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 3/5] wifi: rtlwifi: usb: unify the RX code path Ho Jie Feng
2026-11-09 0:40 ` Ping-Ke Shih [this message]
2026-11-03 9:52 ` [PATCH rtw-next 4/5] wifi: rtlwifi: rtl8192du: enable USB RX aggregation Ho Jie Feng
2026-11-09 1:44 ` Ping-Ke Shih
2026-11-09 1:53 ` Jie Feng
2026-11-09 2:02 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 5/5] wifi: rtlwifi: rtl8192d: let the firmware use all rates Ho Jie Feng
2026-11-09 1:56 ` Ping-Ke Shih
2026-11-09 2:44 ` Jie Feng
2026-11-09 2:58 ` 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=5371f205934a4dfd86cae13ffeebcf7c@realtek.com \
--to=pkshih@realtek.com \
--cc=hjf3108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.