From: Ping-Ke Shih <pkshih@realtek.com>
To: Lewis Robbins <lewis.robbins2@gmail.com>,
"kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: reduce failed to flush queue severity
Date: Wed, 17 Apr 2024 01:42:56 +0000 [thread overview]
Message-ID: <3c6c78248b4144509d733d610991e921@realtek.com> (raw)
In-Reply-To: <d03e8c066a6e464aa61badb252c32b01@realtek.com>
>
> The cause is because packets in hardware TX queue that can't be sent out in time,
> and flush ops with 'drop = false', so driver throws one warning. I don't have
> good idea for now. Maybe, we can add a special debug mask to replace this kind of
> verbose warning with uncertain solution.
I have made a patch [1] as mentioned before. Lewis, please give it a try.
[1] https://lore.kernel.org/linux-wireless/20240417014036.11234-1-pkshih@realtek.com/T/#u
prev parent reply other threads:[~2024-04-17 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 22:59 [PATCH] wifi: rtw88: reduce failed to flush queue severity Lewis Robbins
2024-04-15 1:40 ` Ping-Ke Shih
2024-04-15 16:16 ` Kalle Valo
2024-04-15 23:28 ` Lewis Robbins
2024-04-16 2:57 ` Ping-Ke Shih
2024-04-17 1:42 ` 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=3c6c78248b4144509d733d610991e921@realtek.com \
--to=pkshih@realtek.com \
--cc=kvalo@kernel.org \
--cc=lewis.robbins2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).