[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b1fb50c0-b5ee-dd73-0b8e-f025dd843cbe@st.com>
Date: Mon, 17 Jun 2019 09:54:31 +0200
From: Fabrice Gasnier <fabrice.gasnier@...com>
To: Wolfram Sang <wsa@...-dreams.de>
CC: <pierre-yves.mordret@...com>, <marc.w.gonzalez@...e.fr>,
<fabien.dessenne@...com>, <mcoquelin.stm32@...il.com>,
<alexandre.torgue@...com>, <linux-i2c@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] i2c: i2c-stm32f7: fix the get_irq error cases
On 6/14/19 10:53 PM, Wolfram Sang wrote:
> Hi Fabrice,
>
>> + return irq_event ? irq_event : -ENODEV;
>
> Maybe -ENOENT instead of -ENODEV? I mean you have a dev_err there, so
> the driver core should probably also complain?
>
> You could also shorten the ternary operator to:
>
> return irq_event ? : -E<whatyouprefer>;
>
> However, both are minor nits. If you prefer to keep the patch as is,
> fine with me.
Hi Wolfram,
Thanks for reviewing,
I've sent a v3 with your suggestions.
Regards,
Fabrice
>
> Regards,
>
> Wolfram
>
Powered by blists - more mailing lists