[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZNYIuBjIHItnsyJL@smile.fi.intel.com>
Date: Fri, 11 Aug 2023 13:08:56 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mehdi Djait <mehdi.djait.k@...il.com>
Cc: jic23@...nel.org, mazziesaccount@...il.com,
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 v7 5/7] iio: accel: kionix-kx022a: Refactor driver and
add chip_info structure
On Fri, Aug 11, 2023 at 12:01:23PM +0200, Mehdi Djait wrote:
> On Fri, Aug 11, 2023 at 11:46 AM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Wed, Aug 09, 2023 at 09:11:36PM +0200, Mehdi Djait wrote:
...
> > > + val = min_t(unsigned int, data->chip_info->fifo_length, val);
> >
> > min_t() is a beast. Please, use min() if no special requirement for
> > min_t() here, otherwise explain why.
>
> No actual reason, you suggested min_t or min for a previous version
After the minmax series (see discussion in LKML) I am pretty sure min_t()
shouldn't be used at all or with very minimum cases where people know what
they are doing.
...
> > > + data->fifo_buffer = kmalloc(data->chip_info->fifo_length *
> > > + KX022A_FIFO_SAMPLES_SIZE_BYTES, GFP_KERNEL);
> >
> > kmalloc_array()
>
> Should I send another version for this ?
Sure.
> The usage of kmalloc is quite straightforward and easy to understand here.
Yes, and prone to errors. Multiplication theoretically may overflow and
your code doesn't aware of that, kmalloc_array() does it.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists