Message ID | 2abbbc08-f5bf-28de-e513-5f1074996189@users.sourceforge.net (mailing list archive) |
---|---|
State | Accepted |
Commit | d9bc4a8539a518636cd70d498e94787e32ea8fbe |
Headers | show |
On Fri, Jan 13, 2017 at 06:12:23PM +0100, SF Markus Elfring wrote: > From: Markus Elfring <elfring@users.sourceforge.net> > Date: Fri, 13 Jan 2017 13:37:25 +0100 > > A multiplication for the size determination of a memory allocation > indicated that an array data structure should be processed. > Thus use the corresponding function "kmalloc_array". The previous patch changed a similar call site to use kcalloc() with a similar explanation, the choice of function to translate to seems entirely random since the changelogs don't address the zeroing that kzalloc() and kcalloc() do but kmalloc() and kmalloc_array() don't.
diff --git a/drivers/spi/spi-fsl-spi.c b/drivers/spi/spi-fsl-spi.c index d1b26c9fe950..cdee556037f9 100644 --- a/drivers/spi/spi-fsl-spi.c +++ b/drivers/spi/spi-fsl-spi.c @@ -727,7 +727,8 @@ static int of_fsl_spi_get_chipselects(struct device *dev) return 0; } - pinfo->gpios = kmalloc(ngpios * sizeof(*pinfo->gpios), GFP_KERNEL); + pinfo->gpios = kmalloc_array(ngpios, sizeof(*pinfo->gpios), + GFP_KERNEL); if (!pinfo->gpios) return -ENOMEM; memset(pinfo->gpios, -1, ngpios * sizeof(*pinfo->gpios));