[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a82ba757-3b9c-d54b-76bf-ceef84239295@amazon.com>
Date: Tue, 20 Dec 2022 21:32:11 +0200
From: "Hawa, Hanna" <hhhawa@...zon.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
CC: <wsa@...nel.org>, <linus.walleij@...aro.org>,
<linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-gpio@...r.kernel.org>, <dwmw@...zon.co.uk>,
<benh@...zon.com>, <ronenk@...zon.com>, <talel@...zon.com>,
<jonnyc@...zon.com>, <hanochu@...zon.com>, <farbere@...zon.com>,
<itamark@...zon.com>
Subject: Re: [PATCH v3 1/1] i2c: Set pinctrl recovery info to device pinctrl
On 12/20/2022 9:18 PM, Andy Shevchenko wrote:
>> How you suggest to simplify this?
> Using Elvis operator, which is ?:.
Are you refer to use 'return dev->pins && dev->pins->p ?: NULL;' ?
Can't use Elvis operator in this way, because it will return the result
of 'dev->pins && dev->pins->p' and not the value of 'dev->pins->p'
>
>> I can use 'return dev->pins ? dev->pins->p ?: dev->pins->p : NULL;'
> Have you even try to compile this?
Yup, the code compiled, but i think the first suggestion is more readable.
>
Powered by blists - more mailing lists