[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5BF7CB20.7060502@ti.com>
Date: Fri, 23 Nov 2018 11:40:48 +0200
From: Roger Quadros <rogerq@...com>
To: Arnd Bergmann <arnd@...db.de>
CC: Tony Lindgren <tony@...mide.com>, Rob Herring <robh+dt@...nel.org>,
Beno??t Cousson <bcousson@...libre.com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Suman Anna <s-anna@...com>, Sekhar Nori <nsekhar@...com>,
Tero Kristo <t-kristo@...com>, <nsaulnier@...com>,
<jreeder@...com>, Murali Karicheri <m-karicheri2@...com>,
<woods.technical@...il.com>,
linux-omap <linux-omap@...r.kernel.org>,
<linux-remoteproc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>
Subject: Re: [PATCH 11/17] soc: ti: pruss: add pruss_get()/put() API
On 23/11/18 10:20, Arnd Bergmann wrote:
> On Thu, Nov 22, 2018 at 12:41 PM Roger Quadros <rogerq@...com> wrote:
>
>> +
>> + if (IS_ERR_OR_NULL(rproc))
>> + return ERR_PTR(-EINVAL);
>
>
> Any usage of IS_ERR_OR_NULL() tends to be an indication of a badly
> designed API. Please change this to allow only one of the two to be passed
> around.
The user of this API has to call pru_rproc_get() which never returns NULL.
So IS_ERR() should suffice here.
>
> Arnd
>
cheers,
-roger
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
Powered by blists - more mailing lists