[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZfgWo3ZTHAAhWZ_D@smile.fi.intel.com>
Date: Mon, 18 Mar 2024 12:25:39 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Peng Fan <peng.fan@....com>
Cc: "Peng Fan (OSS)" <peng.fan@....nxp.com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"brgl@...ev.pl" <brgl@...ev.pl>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpiolib: use dev_err when gpiod_configure_flags failed
On Mon, Mar 18, 2024 at 02:03:12AM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH] gpiolib: use dev_err when gpiod_configure_flags failed
> > On Fri, Mar 15, 2024 at 3:02 AM Peng Fan (OSS) <peng.fan@....nxp.com>
> > wrote:
..
> > It's unclear what the use case is and how this does make life easier.
> > We need to know more!
>
> I forgot to add gpio-ranges in gpio node, then it always fail in my driver
> probe to configure pinctrl. So if using dev_err(), it will be easier for
> me to locate the error point.
At least make sure something like the above is in the commit message of the
next version.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists