From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalpesh Solanki <skalpesh942@gmail.com>,
"luka.gejak@linux.dev" <luka.gejak@linux.dev>
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 v2 2/2] wifi: rtw88: ps: Trigger firmware recovery when failing to leave LPS state
Date: Sun, 8 Nov 2026 03:20:53 +0000 [thread overview]
Message-ID: <0439e1c4edd541ada7f38e2e43785088@realtek.com> (raw)
In-Reply-To: <20261107081609.97212-1-skalpesh942@gmail.com>
Kalpesh Solanki <skalpesh942@gmail.com> wrote:
> > For the counter, maybe it is cleaner to revert 2/2 (or rebase and drop
> > it since it is currently the HEAD commit of rtw-next) and send a new
> > patch, since it replaces that line anyway and keeps the current
> > behavior out of the next pull. 1/2 is fine as it is. Ping-Ke, would
> > that work for you, or do you prefer a follow up?
>
> Either way works for me. If Ping-Ke prefers to drop 2/2 from rtw-next, I can
> send the updated patch with the consecutive counter directly. Otherwise I can
> send it as a follow-up on top.
I did force update to drop 2/2. Please respin your patches.
Ping-Ke
next prev parent reply other threads:[~2026-11-08 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 6:31 Kalpesh Solanki
2026-11-07 7:48 ` Luka Gejak
2026-11-07 8:16 ` Kalpesh Solanki
2026-11-08 3:20 ` Ping-Ke Shih [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 3:14 [PATCH v2 1/2] wifi: rtw88: pci: Add DMI quirk for HP Laptop 15s-fr5xxx Kalpesh Solanki
2026-11-03 3:14 ` [PATCH v2 2/2] wifi: rtw88: ps: Trigger firmware recovery when failing to leave LPS state Kalpesh Solanki
2026-11-03 3:17 ` Ping-Ke Shih
2026-11-06 15:33 ` 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=0439e1c4edd541ada7f38e2e43785088@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 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®