From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Azamat Rakhim" <azamatrakhim8@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: remove unused MAX_PATH_NUM defines for other chips
Date: Sun, 15 Feb 2026 18:22:53 -0600 [thread overview]
Message-ID: <DGFYHI8O4AM5.3OX6BUEUNT14U@gmail.com> (raw)
In-Reply-To: <20260215155659.67324-1-azamatrakhim8@gmail.com>
On Sun Feb 15, 2026 at 9:56 AM CST, Azamat Rakhim wrote:
> Remove MAX_PATH_NUM defines for chips not supported by this driver
> (92CS, 8188E, 8192E, 8812A, 8821A, 8814A, 8822B). Only
> MAX_PATH_NUM_8723B is used.
>
> Signed-off-by: Azamat Rakhim <azamatrakhim8@gmail.com>
> ---
LGTM.
Reviewed-by: Ethan Tidmore <ethantidmore06@gmail.com>
Thanks,
ET
prev parent reply other threads:[~2026-02-16 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 15:56 [PATCH] staging: rtl8723bs: remove unused MAX_PATH_NUM defines for other chips Azamat Rakhim
2026-02-16 0:22 ` Ethan Tidmore [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=DGFYHI8O4AM5.3OX6BUEUNT14U@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=azamatrakhim8@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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