From: Luka Gejak <luka.gejak@linux.dev>
To: Ping-Ke Shih <pkshih@realtek.com>,
Kalpesh Solanki <skalpesh942@gmail.com>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 0/2] wifi: rtw88: firmware recovery fixes and LPS hang handling
Date: Mon, 09 Nov 2026 07:21:48 +0100 [thread overview]
Message-ID: <B1CD522C-2CC2-4913-8175-05F0D25CF65F@linux.dev> (raw)
In-Reply-To: <86803b2c13a74ada92ab73e79f38164d@realtek.com>
On November 9, 2026 7:12:52 AM GMT+01:00, Ping-Ke Shih <pkshih@realtek.com>
wrote:
>Luka Gejak <luka.gejak@linux.dev> wrote:
>> On November 9, 2026 3:30:58 AM GMT+01:00, Ping-Ke Shih
><pkshih@realtek.com>
>> wrote:
>> >Kalpesh Solanki <skalpesh942@gmail.com> wrote:
>> >> Changes in v3:
>> >> - Note: v2 patch 1/2 (DMI quirk) is already applied in rtw-next.
>> >> - Add patch 1/2 to clear RTW_FLAG_RESTARTING in rtw_ops_stop()
>> >> with Fixes tag.
>> >> - In patch 2/2:
>> >> - Count consecutive failures before triggering recovery
>> >> (RTW_PS_HANG_MAX_CNT = 3).
>> >> - Reset ps_hang_cnt on successful LPS leave and in
>rtw_core_start().
>> >> - Suppress raw register dump on transient failures to avoid log
>spam.
>> >
>> >The patchset doesn't present in [1] nor [2]. Please wait a while to
>send
>> >newer version after it recovered.
>> >
>> >[1] https://patchwork.kernel.org/project/linux-wireless/list/
>> >[2] https://lore.kernel.org/linux-wireless/
>> >
>> >
>>
>> Hi Ping-Ke,
>>
>> The linux-wireless list is bugged and nothing is appearing on it since
>> 2026-11-06 15:46 UTC. Aren't patches accessible due to
>> linux-kernel@vger.kernel.org being CC'ed?
>
>I think not. I sent patches to linux-wireless, not including linux-kernel,
>before, and the lore and patchwork of linux-wireless can capture the
>patches.
>
>
We are having this conversation on linux-wireless, aren't we? I don't see
it and my lei isn't picking it up.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-11-09 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 8:51 Kalpesh Solanki
2026-11-08 8:51 ` [PATCH v3 1/2] wifi: rtw88: clear RTW_FLAG_RESTARTING in rtw_ops_stop() Kalpesh Solanki
2026-11-08 11:40 ` Luka Gejak
2026-11-08 8:51 ` [PATCH v3 2/2] wifi: rtw88: ps: trigger firmware recovery only after consecutive LPS leave failures Kalpesh Solanki
2026-11-08 11:44 ` Luka Gejak
2026-11-09 2:30 ` [PATCH v3 0/2] wifi: rtw88: firmware recovery fixes and LPS hang handling Ping-Ke Shih
2026-11-09 6:03 ` Luka Gejak
2026-11-09 6:12 ` Ping-Ke Shih
2026-11-09 6:21 ` Luka Gejak [this message]
2026-11-09 6:30 ` Ping-Ke Shih
2026-11-09 6:36 ` 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=B1CD522C-2CC2-4913-8175-05F0D25CF65F@linux.dev \
--to=luka.gejak@linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=skalpesh942@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
all inboxes | Powered by JetHome®