[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32e8ef50-ae45-4001-92b6-1e9e0608b402@kernel.org>
Date: Wed, 28 Aug 2024 15:08:02 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jinjie Ruan <ruanjinjie@...wei.com>, andrew@...n.ch,
sebastian.hesselbarth@...il.com, gregory.clement@...tlin.com,
herve.codina@...tlin.com, qiang.zhao@....com, christophe.leroy@...roup.eu,
thierry.reding@...il.com, jonathanh@...dia.com, nm@...com,
ssantosh@...nel.org, petlozup@...dia.com, pshete@...dia.com,
christophe.jaillet@...adoo.fr, ulf.hansson@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-tegra@...r.kernel.org, jic23@...nel.org
Subject: Re: [PATCH -next 2/8] soc: fsl: cpm1: Simplify with dev_err_probe()
On 28/08/2024 03:58, Jinjie Ruan wrote:
>
>
> On 2024/8/27 21:50, Krzysztof Kozlowski wrote:
>> On 27/08/2024 13:46, Jinjie Ruan wrote:
>>> Use the dev_err_probe() helper to simplify error handling during probe.
>>> This also handle scenario, when EDEFER is returned and useless error
>>> is printed.
>>
>> ? Sorry, this cannot happen. Please point to below code which can defer.
>>
>
> Thank you!
>
> This is not referring to a specific one, but rather the benefits it
> offers,simplify code is the main purpose, if necessary, it will be
> removed in next version.
It just feels like you are doing these in machine way without actually
knowing concepts behind dev_err_probe().
Best regards,
Krzysztof
Powered by blists - more mailing lists