From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"tony0620emma@gmail.com" <tony0620emma@gmail.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"Lukas F . Hartmann" <lukas@mntre.com>
Subject: RE: [PATCH] wifi: rtw88: sdio: Honor the host max_req_size in the RX path
Date: Wed, 2 Aug 2023 00:27:32 +0000 [thread overview]
Message-ID: <d18405744d004aa8a4556db1919c7a12@realtek.com> (raw)
In-Reply-To: <169089906853.212423.17095176293160428610.kvalo@kernel.org>
> -----Original Message-----
> From: Kalle Valo <kvalo@kernel.org>
> Sent: Tuesday, August 1, 2023 10:11 PM
> To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Cc: linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org; jernej.skrabec@gmail.com; Ping-Ke Shih
> <pkshih@realtek.com>; ulf.hansson@linaro.org; tony0620emma@gmail.com; Martin Blumenstingl
> <martin.blumenstingl@googlemail.com>; Lukas F . Hartmann <lukas@mntre.com>
> Subject: Re: [PATCH] wifi: rtw88: sdio: Honor the host max_req_size in the RX path
>
> Ping, should I take or drop the patch? It wasn't quite clear for me.
Please drop this patch, because this patch still not fixes problem on Lukas' platform.
I gave my reviewed-by too early. Sorry for that.
Ping-Ke
prev parent reply other threads:[~2023-08-02 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 19:57 [PATCH] wifi: rtw88: sdio: Honor the host max_req_size in the RX path Martin Blumenstingl
2023-07-10 0:36 ` Ping-Ke Shih
[not found] ` <87pm4w3rjp.fsf@mntre.com>
2023-07-14 0:34 ` Ping-Ke Shih
2023-07-26 17:37 ` Martin Blumenstingl
2023-07-27 1:44 ` Ping-Ke Shih
2023-08-01 14:11 ` Kalle Valo
2023-08-02 0:27 ` 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=d18405744d004aa8a4556db1919c7a12@realtek.com \
--to=pkshih@realtek.com \
--cc=jernej.skrabec@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas@mntre.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=tony0620emma@gmail.com \
--cc=ulf.hansson@linaro.org \
/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