From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>,
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, 9 Nov 2026 06:12:52 +0000 [thread overview]
Message-ID: <86803b2c13a74ada92ab73e79f38164d@realtek.com> (raw)
In-Reply-To: <27E9A60D-26F6-41D6-B74F-7DEF998C8498@linux.dev>
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.
next prev parent reply other threads:[~2026-11-09 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 8:51 [PATCH v3 0/2] wifi: rtw88: firmware recovery fixes and LPS hang handling 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 [this message]
2026-11-09 6:21 ` Luka Gejak
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=86803b2c13a74ada92ab73e79f38164d@realtek.com \
--to=pkshih@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--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 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.