From: Ping-Ke Shih <pkshih@realtek.com>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"martin.blumenstingl@googlemail.com"
<martin.blumenstingl@googlemail.com>
Subject: RE: rtl8822cs, mainline 6.16-rc7: kernel reports ' unsupported rf path'
Date: Thu, 24 Jul 2025 07:59:59 +0000 [thread overview]
Message-ID: <e34a045492ae454cb255aca78d2b9641@realtek.com> (raw)
In-Reply-To: <B89A3F05-FE7E-4AE8-8F75-34DBBC285C0E@gmail.com>
Piotr Oniszczuk <piotr.oniszczuk@gmail.com> wrote:
> > Wiadomość napisana przez Ping-Ke Shih <pkshih@realtek.com> w dniu 24 lip 2025, o godz. 02:52:
> >
> > I sent a patch [1] with a change that check RTW_FLAG_POWERON flag first,
> > so things will be the same as this final try. Still want you test the patch
> > again, and give me a Tested-by tag there. Thanks.
> >
> > [1] https://lore.kernel.org/linux-wireless/20250724004815.7043-1-pkshih@realtek.com/T/#u
> >
> >
>
> I give test and with this patch issue disappear.
> thx for fixing this!
>
> pla add
>
> Tested-by: Piotr Oniszczuk <piotr.oniszczuk@gmail.com <mailto:piotr.oniszczuk@gmail.com>>
Could you please add this tag to the patch? Then, your Tested-by will be added
into commit message during getting merged.
prev parent reply other threads:[~2025-07-24 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 13:29 rtl8822cs, mainline 6.16-rc7: kernel reports ' unsupported rf path' Piotr Oniszczuk
2025-07-23 0:52 ` Ping-Ke Shih
2025-07-23 7:34 ` Piotr Oniszczuk
2025-07-23 7:50 ` Ping-Ke Shih
2025-07-23 8:02 ` Piotr Oniszczuk
2025-07-23 8:19 ` Ping-Ke Shih
2025-07-23 8:46 ` Piotr Oniszczuk
2025-07-23 9:07 ` Ping-Ke Shih
2025-07-23 11:14 ` Bitterblue Smith
2025-07-23 12:23 ` Ping-Ke Shih
2025-07-23 13:02 ` Piotr Oniszczuk
2025-07-24 0:52 ` Ping-Ke Shih
2025-07-24 7:55 ` Piotr Oniszczuk
2025-07-24 7:59 ` 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=e34a045492ae454cb255aca78d2b9641@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=piotr.oniszczuk@gmail.com \
--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.