From: sashiko-bot@kernel.org
To: "Manish Baing" <manishbaing2789@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 4/7] hwmon: nct6683: Use zero-initialization instead of memset()
Date: Sat, 30 May 2026 22:35:03 +0000 [thread overview]
Message-ID: <20260530223503.795391F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260530221353.159461-5-manishbaing2789@gmail.com>
> Reduce the scope of 'struct resource res' by moving it inside the for-loop
> and using empty brace initialization (= {}). This ensures the structure is
> safely zero-initialized on every iteration, allowing for the safe removal
> of explicit memset() call.
>
> No functional change.
>
> Signed-off-by: Manish Baing <manishbaing2789@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260530221353.159461-1-manishbaing2789@gmail.com?part=4
next prev parent reply other threads:[~2026-05-30 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 22:13 [PATCH 0/7] hwmon: zero-initialization instead of memset Manish Baing
2026-05-30 22:13 ` [PATCH 1/7] hwmon: drivetemp: Use zero-initialization instead of memset() Manish Baing
2026-05-30 22:17 ` sashiko-bot
2026-05-30 22:13 ` [PATCH 2/7] hwmon: f71882fg: " Manish Baing
2026-05-30 22:18 ` sashiko-bot
2026-05-30 22:13 ` [PATCH 3/7] hwmon: ltc2947-core: " Manish Baing
2026-05-30 22:32 ` sashiko-bot
2026-05-30 22:13 ` [PATCH 4/7] hwmon: nct6683: " Manish Baing
2026-05-30 22:35 ` sashiko-bot [this message]
2026-05-30 22:13 ` [PATCH 5/7] hwmon: nct6775-platform: " Manish Baing
2026-05-30 22:37 ` sashiko-bot
2026-05-30 22:13 ` [PATCH 6/7] hwmon: pmbus: adm1266: " Manish Baing
2026-05-30 22:40 ` sashiko-bot
2026-05-30 22:13 ` [PATCH 7/7] hwmon: it87: " Manish Baing
2026-05-30 22:47 ` sashiko-bot
2026-06-06 19:22 ` 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=20260530223503.795391F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=manishbaing2789@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.