From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Leo.Li" <leo.li@realtek.com>
Subject: Re: [PATCH] wifi: rtw89: disable txptctrl IMR to avoid flase alarm
Date: Thu, 21 Mar 2024 08:01:17 +0200 [thread overview]
Message-ID: <87jzlw9l8y.fsf@kernel.org> (raw)
In-Reply-To: <2eefd73994778c1fa1dc03acf04708d686ec3185.camel@realtek.com> (Ping-Ke Shih's message of "Thu, 21 Mar 2024 05:33:07 +0000")
Ping-Ke Shih <pkshih@realtek.com> writes:
> On Thu, 2024-03-21 at 07:12 +0200, Kalle Valo wrote:
>>
>> Ping-Ke Shih <pkshih@realtek.com> writes:
>>
>> > From: Chia-Yuan Li <leo.li@realtek.com>
>> >
>> > The hardware command parser of txptctrl (TX protocol control) has overly
>> > stringent timeout conditions, which results in false alarm. So disable it.
>> >
>> > Signed-off-by: Chia-Yuan Li <leo.li@realtek.com>
>> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
>>
>> I'm in the To field, do you maybe want me to take this to wireless tree?
>>
>
> No, it should go via rtw.git. I just send this patch as usual.
Ok.
> Should I change to wireless mailing list as To field and no need to
> add you in neither To field nor Cc field in the future?
Yes, please drop me from To and Cc fields. And if there's an important
fix you want to go to wireless tree please label it as "[PATCH
wireless]" (or comment on the patch) and assign to me on patchwork.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-03-21 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 2:56 [PATCH] wifi: rtw89: disable txptctrl IMR to avoid flase alarm Ping-Ke Shih
2024-03-21 5:12 ` Kalle Valo
2024-03-21 5:33 ` Ping-Ke Shih
2024-03-21 6:01 ` Kalle Valo [this message]
2024-03-21 6:06 ` Ping-Ke Shih
2024-03-21 6:18 ` Kalle Valo
2024-03-21 6:21 ` Ping-Ke Shih
2024-03-26 1:29 ` Ping-Ke Shih
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=87jzlw9l8y.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=leo.li@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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