[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <171214017002.130010.3184925664722710524.b4-ty@collabora.com>
Date: Wed, 3 Apr 2024 12:31:58 +0200
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
To: Matthias Brugger <matthias.bgg@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Moudy Ho <moudy.ho@...iatek.com>,
"Jason-JH . Lin" <jason-jh.lin@...iatek.com>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org,
Chun-Kuang Hu <chunkuang.hu@...nel.org>,
NĂcolas F. R. A. Prado <nfraprado@...labora.com>
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
kernel@...labora.com
Subject: Re: [PATCH v2] soc: mediatek: cmdq: Don't log an error when gce-client-reg is not found
On Thu, 29 Feb 2024 14:51:08 -0500, NĂcolas F. R. A. Prado wrote:
> Most of the callers to this function do not require CMDQ support, it is
> optional, so the missing property shouldn't cause an error message.
> However, it could result on degraded performance, so the fact that it's
> missing should still be alerted. Furthermore, the callers that do
> require CMDQ support already log at the error level when an error is
> returned.
>
> [...]
Applied to v6.9-next/soc, thanks!
[1/1] soc: mediatek: cmdq: Don't log an error when gce-client-reg is not found
commit: ef964918d42b9d9cf534754f82ccdaa402783ecd
Cheers,
Angelo
Powered by blists - more mailing lists