From: Raag Jadav <raag.jadav@intel.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org,
linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, dmitry.torokhov@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org, sre@kernel.org,
jic23@kernel.org, przemyslaw.kitszel@intel.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-sound@vger.kernel.org,
linux-pm@vger.kernel.org, linux-iio@vger.kernel.org,
Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v4 12/20] regulator: cros-ec: use devm_kmemdup_array()
Date: Mon, 10 Feb 2025 12:18:58 +0530 [thread overview]
Message-ID: <20250210064906.2181867-13-raag.jadav@intel.com> (raw)
In-Reply-To: <20250210064906.2181867-1-raag.jadav@intel.com>
Convert to use devm_kmemdup_array() and while at it, make the size robust
against type changes.
Signed-off-by: Raag Jadav <raag.jadav@intel.com>
---
drivers/regulator/cros-ec-regulator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/cros-ec-regulator.c b/drivers/regulator/cros-ec-regulator.c
index fb9643ed7a49..fb0767b33a36 100644
--- a/drivers/regulator/cros-ec-regulator.c
+++ b/drivers/regulator/cros-ec-regulator.c
@@ -138,8 +138,8 @@ static int cros_ec_regulator_init_info(struct device *dev,
data->num_voltages =
min_t(u16, ARRAY_SIZE(resp.voltages_mv), resp.num_voltages);
data->voltages_mV =
- devm_kmemdup(dev, resp.voltages_mv,
- sizeof(u16) * data->num_voltages, GFP_KERNEL);
+ devm_kmemdup_array(dev, resp.voltages_mv, data->num_voltages,
+ sizeof(resp.voltages_mv[0]), GFP_KERNEL);
if (!data->voltages_mV)
return -ENOMEM;
--
2.34.1
next prev parent reply other threads:[~2025-02-10 6:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:48 [PATCH v4 00/20] Split devres APIs to device/devres.h and introduce devm_kmemdup_array() Raag Jadav
2025-02-10 6:48 ` [PATCH v4 01/20] driver core: Split devres APIs to device/devres.h Raag Jadav
2025-02-10 14:08 ` kernel test robot
2025-02-10 14:30 ` kernel test robot
2025-02-10 15:23 ` Andy Shevchenko
2025-02-10 21:35 ` Raag Jadav
2025-02-11 7:36 ` Arnd Bergmann
2025-02-11 9:27 ` Andy Shevchenko
2025-02-11 9:39 ` Arnd Bergmann
2025-02-11 10:11 ` Andy Shevchenko
2025-02-11 10:23 ` Arnd Bergmann
2025-02-11 11:37 ` Andy Shevchenko
2025-02-11 11:56 ` Arnd Bergmann
2025-02-11 12:10 ` Andy Shevchenko
2025-02-11 12:57 ` Raag Jadav
2025-02-10 18:43 ` kernel test robot
2025-02-10 6:48 ` [PATCH v4 02/20] iio: imu: st_lsm9ds0: Replace device.h with what is needed Raag Jadav
2025-02-10 6:48 ` [PATCH v4 03/20] devres: Introduce devm_kmemdup_array() Raag Jadav
2025-02-10 6:48 ` [PATCH v4 04/20] pinctrl: intel: copy communities using devm_kmemdup_array() Raag Jadav
2025-02-10 6:48 ` [PATCH v4 05/20] pinctrl: baytrail: " Raag Jadav
2025-02-10 6:48 ` [PATCH v4 06/20] pinctrl: cherryview: use devm_kmemdup_array() Raag Jadav
2025-02-10 6:48 ` [PATCH v4 07/20] pinctrl: tangier: " Raag Jadav
2025-02-10 6:48 ` [PATCH v4 08/20] pinctrl: pxa2xx: " Raag Jadav
2025-02-10 6:48 ` [PATCH v4 09/20] input: sparse-keymap: " Raag Jadav
2025-02-10 6:48 ` [PATCH v4 10/20] input: ipaq-micro-keys: " Raag Jadav
2025-02-10 6:48 ` [PATCH v4 11/20] regulator: devres: " Raag Jadav
2025-02-10 6:48 ` Raag Jadav [this message]
2025-02-10 6:48 ` [PATCH v4 13/20] power: supply: sc27xx: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 14/20] iio: adc: xilinx-xadc-core: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 15/20] ASoC: Intel: avs: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 16/20] ASoC: hdac_hdmi: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 17/20] ASoC: tlv320dac33: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 18/20] ASoC: uda1380: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 19/20] ASoC: meson: axg-tdm-interface: " Raag Jadav
2025-02-10 6:49 ` [PATCH v4 20/20] ASoC: uniphier: " Raag Jadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250210064906.2181867-13-raag.jadav@intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rafael@kernel.org \
--cc=sre@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).