[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOddp3LBHi/3c5XN@smile.fi.intel.com>
Date: Thu, 24 Aug 2023 16:39:51 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Matti Vaittinen <mazziesaccount@...il.com>
Cc: Mehdi Djait <mehdi.djait.k@...il.com>, jic23@...nel.org,
krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
lars@...afoo.de, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v8 7/7] iio: accel: Add support for Kionix/ROHM
KX132-1211 accelerometer
On Thu, Aug 24, 2023 at 03:51:18PM +0300, Matti Vaittinen wrote:
> On 8/24/23 15:02, Andy Shevchenko wrote:
> > On Wed, Aug 23, 2023 at 11:16:41PM +0200, Mehdi Djait wrote:
...
> > > + .yes_ranges = &kx132_volatile_ranges[0],
> >
> >
> > This should be the same as
> >
> > .yes_ranges = kx132_volatile_ranges,
> >
>
> The driver uses &kx132_volatile_ranges[0] in a few places (for kx022a) so I
> believe this is okay. Well, I know I am biased as I do personally find
> &kx132_volatile_ranges[0] clearer. Here we point to the first element in an
> array - and yes, it may be I am minority here - but at least I wouldn't ask
> for changing this.
It's a minor thingy, can be ignored.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists