[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87fscgdska.fsf@kernel.org>
Date: Thu, 12 Jan 2023 11:13:09 +0200
From: Kalle Valo <kvalo@...nel.org>
To: Jeffrey Hugo <jeffrey.l.hugo@...il.com>
Cc: Baochen Qiang <quic_bqiang@...cinc.com>,
manivannan.sadhasivam@...aro.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, ath11k@...ts.infradead.org
Subject: Re: [PATCH] bus: mhi: host: Change the log levels for SYS_ERR event
Jeffrey Hugo <jeffrey.l.hugo@...il.com> writes:
> Why was this not sent to the MHI mailing list?
>
> On Tue, Jan 3, 2023 at 7:19 PM Baochen Qiang <quic_bqiang@...cinc.com> wrote:
>>
>> Currently no log printed when SYS_ERR happens, this makes
>> debug quite hard, so change log level to make it noisy.
>
> You are going to need to explain this more.
> There are two drivers in the upstream kernel that are MHI clients -
> pci_generic and ath11k.
> I'm assuming that you care about ath11k because you included that mail list.
> In ath11k_mhi_op_status_cb() I see a warning message printed when the
> syserr callback is triggered.
> I see something similar in pci_generic.
>
> Looks like a log is printed when SYS_ERR happens in all possible
> scenarios, so I don't understand the point of this change.
> Particularly given that dev_dbg messages can be trivially enabled.
Also the error messages are not very informative, especially if there
are three identical messages it's hard to track down which code path is
triggering them. If these are changed to error messages, I would prefer
to improve them as well.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists