[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6991a517301a46159085a0b06d43f319@realtek.com>
Date: Fri, 13 Oct 2023 01:11:32 +0000
From: Ping-Ke Shih <pkshih@...ltek.com>
To: Chukun Pan <amadeus@....edu.cn>
CC: Kalle Valo <kvalo@...nel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
> -----Original Message-----
> From: Chukun Pan <amadeus@....edu.cn>
> Sent: Thursday, October 12, 2023 10:01 PM
> To: Ping-Ke Shih <pkshih@...ltek.com>
> Cc: Kalle Valo <kvalo@...nel.org>; linux-wireless@...r.kernel.org; linux-kernel@...r.kernel.org; Chukun
> Pan <amadeus@....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
Powered by blists - more mailing lists