[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X7ADFLwEpUHkTiT+@kroah.com>
Date: Sat, 14 Nov 2020 17:17:24 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Michal Simek <michal.simek@...inx.com>,
linux-iio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v2 1/4] device: provide devm_krealloc_array()
On Sat, Nov 14, 2020 at 03:46:41PM +0000, Jonathan Cameron wrote:
> On Mon, 2 Nov 2020 15:22:25 +0100
> Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> > From: Bartosz Golaszewski <bgolaszewski@...libre.com>
> >
> > When allocating an array of elements, users should check for
> > multiplication overflow or preferably use one of the provided helpers
> > like: devm_kmalloc_array().
> >
> > This provides devm_krealloc_array() for users who want to reallocate
> > managed arrays.
> >
> > Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
>
> +CC Greg KH.
>
> As this is going into a very generic place I'd like a relevant ack.
> That file is a bit of a wild west for acks, but Greg seems most
> appropriate person.
>
> So Greg, any comments on this one?
As there is only 1 user of this function in the patch series, you don't
save any extra code space here, I don't think this is worth it.
We are seeing less and less gains from these new devm_* additions, and
only more confusion and problems with them. So perhaps don't add this?
I don't think it is needed.
thanks,
greg k-h
Powered by blists - more mailing lists