From: Manish Baing <manishbaing2789@gmail.com>
To: linux@roeck-us.net, jdelvare@suse.com, nuno.sa@analog.com
Cc: abdurrahman@nexthop.ai, bartosz.golaszewski@oss.qualcomm.com,
linusw@kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
me@brighamcampbell.com, manishbaing2789@gmail.com
Subject: [PATCH 0/7] hwmon: zero-initialization instead of memset
Date: Sat, 30 May 2026 22:13:45 +0000 [thread overview]
Message-ID: <20260530221353.159461-1-manishbaing2789@gmail.com> (raw)
Hi all,
This patch series cleans up memory initialization across several
hardware monitoring (hwmon) drivers by replacing explicit memset() calls
with empty brace initialization (= {}).
Following similar cleanups in the IIO subsystem [1], this series updates
these drivers to stop using memset() for stack memory initialization.
As noted in those discussions [2], using empty brace initialization (= {})
is the preferred approach.
Beyond simple replacements, a few drivers (nct6683, nct6775-platform, it87)
were using memset() inside a for-loop. To fix this, the variable
declarationwas moved directly inside the loop and zero-initialized there.
This safely resets the data on every iteration and makes the code much
cleaner.
Testing:
- Compiled all modified files using `make W=1` with no warnings or errors.
[1]: https://lore.kernel.org/all/20250611-iio-zero-init-stack-with-instead-of-memset-v1-0-ebb2d0a24302@baylibre.com/
[2]: https://lore.kernel.org/linux-iio/202505090942.48EBF01B@keescook/
Manish Baing (7):
hwmon: drivetemp: Use zero-initialization instead of memset()
hwmon: f71882fg: Use zero-initialization instead of memset()
hwmon: ltc2947-core: Use zero-initialization instead of memset()
hwmon: nct6683: Use zero-initialization instead of memset()
hwmon: nct6775-platform: Use zero-initialization instead of memset()
hwmon: pmbus: adm1266: Use zero-initialization instead of memset()
hwmon: it87: Use zero-initialization instead of memset()
drivers/hwmon/drivetemp.c | 3 +--
drivers/hwmon/f71882fg.c | 4 +---
drivers/hwmon/it87.c | 3 +--
drivers/hwmon/ltc2947-core.c | 4 +---
drivers/hwmon/nct6683.c | 4 ++--
drivers/hwmon/nct6775-platform.c | 4 ++--
drivers/hwmon/pmbus/adm1266.c | 4 +---
7 files changed, 9 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-30 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 22:13 Manish Baing [this message]
2026-05-30 22:13 ` [PATCH 1/7] hwmon: drivetemp: Use zero-initialization instead of memset() Manish Baing
2026-05-30 22:13 ` [PATCH 2/7] hwmon: f71882fg: " Manish Baing
2026-05-30 22:13 ` [PATCH 3/7] hwmon: ltc2947-core: " Manish Baing
2026-05-30 22:13 ` [PATCH 4/7] hwmon: nct6683: " Manish Baing
2026-05-30 22:13 ` [PATCH 5/7] hwmon: nct6775-platform: " Manish Baing
2026-05-30 22:13 ` [PATCH 6/7] hwmon: pmbus: adm1266: " Manish Baing
2026-05-30 22:13 ` [PATCH 7/7] hwmon: it87: " Manish Baing
2026-06-06 19:22 ` Manish Baing
2026-06-07 16:12 ` [PATCH 0/7] hwmon: zero-initialization instead of memset Guenter Roeck
2026-06-25 16:04 ` Manish Baing
2026-06-26 1:59 ` Guenter Roeck
2026-06-26 4:43 ` Manish Baing
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=20260530221353.159461-1-manishbaing2789@gmail.com \
--to=manishbaing2789@gmail.com \
--cc=abdurrahman@nexthop.ai \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=jdelvare@suse.com \
--cc=linusw@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=me@brighamcampbell.com \
--cc=nuno.sa@analog.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®