[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75b5875d-fa88-3995-6776-ac9a67a3de3c@kontron.de>
Date: Fri, 2 Aug 2019 07:59:44 +0000
From: Schrempf Frieder <frieder.schrempf@...tron.de>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
CC: "shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
"linux-imx@....com" <linux-imx@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"geert+renesas@...der.be" <geert+renesas@...der.be>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
Jiri Slaby <jslaby@...e.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 2/3] serial: sh-sci: Remove check for specific
mctrl_gpio_init() return value
On 01.08.19 22:39, Uwe Kleine-König wrote:
> On Thu, Aug 01, 2019 at 06:45:24PM +0000, Schrempf Frieder wrote:
>> From: Frieder Schrempf <frieder.schrempf@...tron.de>
>>
>> Now that the mctrl_gpio code returns NULL instead of ERR_PTR(-ENOSYS)
>> in cases when CONFIG_GPIOLIB is disabled, we can safely remove this
>> check.
>
> I would mention -ENOSYS in the Subject line. Something like:
>
> serial: sh-sci: don't check for mctrl_gpio_init returning -ENOSYS
>
> Now that the mctrl_gpio code returns NULL instead of
> ERR_PTR(-ENOSYS) if CONFIG_GPIOLIB is disabled, we can safely
> remove this check.
Indeed, I failed to come up with a better subject line. I will adopt
your proposal.
> Thanks
> Uwe
>
Powered by blists - more mailing lists