From: Ping-Ke Shih <pkshih@realtek.com>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Kalle Valo <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 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
Date: Fri, 13 Oct 2023 01:11:32 +0000 [thread overview]
Message-ID: <6991a517301a46159085a0b06d43f319@realtek.com> (raw)
In-Reply-To: <20231012140120.891411-1-amadeus@jmu.edu.cn>
> -----Original Message-----
> From: Chukun Pan <amadeus@jmu.edu.cn>
> Sent: Thursday, October 12, 2023 10:01 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kalle Valo <kvalo@kernel.org>; linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org; Chukun
> Pan <amadeus@jmu.edu.cn>
> Subject: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
>
> The rtw88 driver throws a useless Call Trace when the rtl8812bu
> or rtl8822be wifi modules fail to write the RF mode table.
Why do you think this trace is useless? As I see, there is more than one callers.
Did you meet a real case it throws this trace? If yes, how about the frequency?
Ping-Ke
next prev parent reply other threads:[~2023-10-13 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:01 [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail Chukun Pan
2023-10-13 1:11 ` Ping-Ke Shih [this message]
2023-10-13 2:38 ` Chukun Pan
2023-10-13 4:23 ` Kalle Valo
2023-10-22 9:09 ` Chukun Pan
2023-10-23 2:22 ` Ping-Ke Shih
2023-10-25 4:01 ` Chukun Pan
2023-10-23 8:21 ` Kalle Valo
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=6991a517301a46159085a0b06d43f319@realtek.com \
--to=pkshih@realtek.com \
--cc=amadeus@jmu.edu.cn \
--cc=kvalo@kernel.org \
--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 NNTP newsgroup(s).