From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "Larry.Finger\@lwfinger.net" <Larry.Finger@lwfinger.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"s.hauer\@pengutronix.de" <s.hauer@pengutronix.de>
Subject: Re: Question about rtw88 patches
Date: Sat, 15 Apr 2023 08:36:29 +0300 [thread overview]
Message-ID: <873551so4i.fsf@kernel.org> (raw)
In-Reply-To: <e8e70392bb38ee44f29fd0dc2522daa8340cf609.camel@realtek.com> (Ping-Ke Shih's message of "Sat, 15 Apr 2023 04:00:28 +0000")
Ping-Ke Shih <pkshih@realtek.com> writes:
> On Fri, 2023-04-14 at 14:50 -0500, Larry Finger wrote:
>>
>> Kalle,
>>
>> Has something gone wrong with Sasha's rtw88 patches to fix the hardware queue
>> selection in rtw88 [1], and the corresponding rfe field width fix [2]. These two
>> patches are included in my GitHub repo for rtw88, and they fix the ubiquitous
>> "timed out to flush queue" warnings.
>>
>> Larry
>>
>> [1]
>> https://lore.kernel.org/linux-wireless/20230404072508.578056-2-s.hauer@pengutronix.de/
>> [2]
>> https://lore.kernel.org/linux-wireless/20230404072508.578056-3-s.hauer@pengutronix.de/
>>
>
> Hi Larry,
>
> I think this is because I have some suggestions of [2] to improve further.
> Do you think we can take this temporary version in advance?
Yeah, I put the patches in patchwork to "Changes Requested" as Ping had
comments for them:
https://patchwork.kernel.org/project/linux-wireless/list/?series=736690&state=*&order=date
My assumption was that there will be v3.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-15 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 19:50 Question about rtw88 patches Larry Finger
2023-04-15 4:00 ` Ping-Ke Shih
2023-04-15 5:36 ` Kalle Valo [this message]
2023-04-15 17:22 ` Larry Finger
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=873551so4i.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=s.hauer@pengutronix.de \
/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.