From: sashiko-bot@kernel.org
To: bakshansky.lists@gmail.com
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: (coretemp) fix coding style issues
Date: Sat, 16 May 2026 12:26:01 +0000 [thread overview]
Message-ID: <20260516122602.56C85C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260516114253.5466-3-bakshansky.lists@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] A blank line was incorrectly added inside a contiguous block of declarations in `create_core_attrs()`, splitting the variable declarations.
--
commit fd6a696ecbdee696c6e67fb77fb06e3c1baa31cc
Author: Roman Bakshansky <bakshansky.lists@gmail.com>
hwmon: (coretemp) fix coding style issues
This commit addresses several coding style warnings reported by checkpatch.pl.
It updates header inclusions, adds missing blank lines, combines split strings,
and reorders the __initconst attribute.
> diff --git a/drivers/hwmon/coretemp.c b/drivers/hwmon/coretemp.c
> index c722b1d8e4804..a79c2d65a2bee 100644
> --- a/drivers/hwmon/coretemp.c
> +++ b/drivers/hwmon/coretemp.c
[ ... ]
> @@ -424,6 +423,7 @@ static ssize_t show_temp(struct device *dev,
> static int create_core_attrs(struct temp_data *tdata, struct device *dev)
> {
> int i;
> +
This isn't a bug, but does this newly added blank line split a contiguous
block of variable declarations?
The static array rd_ptr is also a variable declaration, so this separates it
from the int i declaration. It looks like checkpatch.pl might have misparsed
the complex function pointer array declaration as a statement.
> static ssize_t (*const rd_ptr[TOTAL_ATTRS]) (struct device *dev,
> struct device_attribute *devattr, char *buf) = {
> show_label, show_crit_alarm, show_temp, show_tjmax,
> show_ttarget };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260516114253.5466-1-bakshansky.lists@gmail.com?part=2
next prev parent reply other threads:[~2026-05-16 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 11:42 [PATCH 0/2] hwmon: (coretemp) replace hardcoded core count and fix style issues bakshansky.lists
2026-05-16 11:42 ` [PATCH 1/2] hwmon: (coretemp) replace hardcoded core count with dynamic value bakshansky.lists
2026-05-16 12:16 ` sashiko-bot
2026-05-16 12:47 ` Guenter Roeck
2026-05-16 12:48 ` Guenter Roeck
2026-05-16 11:42 ` [PATCH 2/2] hwmon: (coretemp) fix coding style issues bakshansky.lists
2026-05-16 12:26 ` sashiko-bot [this message]
2026-05-16 12:50 ` Guenter Roeck
2026-05-16 15:10 ` bakshansky.lists
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=20260516122602.56C85C19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bakshansky.lists@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox