[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b457c30-6093-437b-b9af-44c3a768020f@amlogic.com>
Date: Tue, 25 Jun 2024 17:33:22 +0800
From: Kelvin Zhang <kelvin.zhang@...ogic.com>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>,
Junyi Zhao <junyi.zhao@...ogic.com>
Cc: Jerome Brunet <jbrunet@...libre.com>,
Kelvin Zhang via B4 Relay <devnull+kelvin.zhang.amlogic.com@...nel.org>,
Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-pwm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v8 1/2] pwm: meson: Add support for Amlogic S4 PWM
On 2024/6/17 22:11, Uwe Kleine-König wrote:
> Hello,
>
> On Mon, Jun 17, 2024 at 04:44:13PM +0800, Junyi Zhao wrote:
>>>> So yes, please use dev_err_probe() also to handle
>>>> devm_add_action_or_reset().
>>> My point here is also that devm_add_action_or_reset() can only fail on
>>> memory allocation, like (devm_)kzalloc. Looking around the kernel, we
>>> tend to not add messages for that and just return the error code,
>>> presumably because those same 'out of memory' messages would proliferate
>>> everywhere.
>> Hi Uwe, I didnt get the clear point.
>> So, if we need "return ret" directly? or keep "dev_err_probe()" to print?
> Please keep the dev_err_probe(). There is a problem with that approach
> (as Jerome pointed out), but that is about to be addressed in driver
> core code.
>
Hi Uwe,
For this patchset, is there anything that needs improvement?
Thanks!
> Best regards
> Uwe
Powered by blists - more mailing lists