[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BibF5A9sw=fLr3DXLf9LXYdxWy=aK7KCE3L0bt5eX+9Q@mail.gmail.com>
Date: Wed, 18 Dec 2019 12:09:42 -0300
From: Fabio Estevam <festevam@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Peng Fan <peng.fan@....com>,
"jason@...edaemon.net" <jason@...edaemon.net>,
"gregory.clement@...tlin.com" <gregory.clement@...tlin.com>,
"sebastian.hesselbarth@...il.com" <sebastian.hesselbarth@...il.com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"mripard@...nel.org" <mripard@...nel.org>,
"wens@...e.org" <wens@...e.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/2] pinctrl: mvebu: armada-37xx: use use platform api
Hi Andrew,
On Wed, Dec 18, 2019 at 12:00 PM Andrew Lunn <andrew@...n.ch> wrote:
> Hi Fabio
>
> Look closer. This is not about returning an error, it is about
> printing an error.
>
> I think the API could better. A %ie formatter would make a lot of
> sense, so avoiding the ERR_PTR().
Yes, I think that returning the error like:
dev_err(dev, "Couldn't determine irq count: %d\n", nr_irq_parent);
would make the code cleaner.
Maybe just a matter of taste though ;-)
Powered by blists - more mailing lists