From: Ping-Ke Shih <pkshih@realtek.com>
To: "luka.gejak@linux.dev" <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Straube" <straube.linux@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH v2 1/4] wifi: rtw88: 8723bs: add the core handling required by RTL8723BS
Date: Fri, 24 Jul 2026 09:29:41 +0000 [thread overview]
Message-ID: <47e555f89dce4a0997e19d7ba753dbb5@realtek.com> (raw)
In-Reply-To: <20260722200337.135150-2-luka.gejak@linux.dev>
luka.gejak@linux.dev <luka.gejak@linux.dev> wrote:
> From: Luka Gejak <luka.gejak@linux.dev>
>
> Several of those need explaining, because the reason is not visible in
> the code:
>
It seems like you misunderstood what I meant. You should add each necessary
functions by individual patch. Don't mix them.
(Sorry, I'd reply the cover letter you wrote next week.)
If you consider these all are necessary, send preparations as first patchset,
and start to add RTL8723BS by second patchset. With a large patchset, I can't
respond quickly.
Ping-Ke
next prev parent reply other threads:[~2026-07-24 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 20:03 [PATCH v2 0/4] wifi: rtw88: add RTL8723B/RTL8723BS support luka.gejak
2026-07-22 20:03 ` [PATCH v2 1/4] wifi: rtw88: 8723bs: add the core handling required by RTL8723BS luka.gejak
2026-07-24 9:29 ` Ping-Ke Shih [this message]
2026-07-22 20:03 ` [PATCH v2 2/4] wifi: rtw88: 8723b: add RTL8723B chip support luka.gejak
2026-07-22 20:03 ` [PATCH v2 3/4] wifi: rtw88: 8723bs: enable building the RTL8723BS driver luka.gejak
2026-07-22 20:03 ` [PATCH v2 4/4] MAINTAINERS: add entry for the RTL8723B rtw88 driver luka.gejak
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=47e555f89dce4a0997e19d7ba753dbb5@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=pbrobinson@gmail.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=straube.linux@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