[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2610031.B6nN8fjXyO@wuerfel>
Date: Mon, 02 May 2016 20:41:11 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Javier Martinez Canillas <javier@....samsung.com>,
linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Kamil Debski <k.debski@...sung.com>,
Jeongtae Park <jtp.park@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
linux-media@...r.kernel.org,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH] s5p-mfc: Don't try to put pm->clock if lookup failed
On Monday 02 May 2016 13:27:54 Javier Martinez Canillas wrote:
> Failing to get the struct s5p_mfc_pm .clock is a non-fatal error so the
> clock field can have a errno pointer value. But s5p_mfc_final_pm() only
> checks if .clock is not NULL before attempting to unprepare and put it.
>
> This leads to the following warning in clk_put() due s5p_mfc_final_pm():
>
Better assign the pointer to NULL in case of a non-fatal error
return code. That way, the reader doesn't have to wonder why you
have the IS_ERR_OR_NULL() check here.
Arnd
Powered by blists - more mailing lists