From: sashiko-bot@kernel.org
To: "Binbin Zhou" <zhoubinbin@loongson.cn>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 4/7] thermal/drivers/loongson2: Use bitfields and per-SoC thermal ops
Date: Mon, 28 Sep 2026 04:52:59 +0000 [thread overview]
Message-ID: <20260928045300.65DBF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <16875dca6130410dbd885c7af347c161c9417511.1790561983.git.zhoubinbin@loongson.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] thermal: misspelled function name loognson2_thermal_set_trips()
--
commit 50b534520f37f80d31dade061303171856000e41
Author: Binbin Zhou <zhoubinbin@loongson.cn>
thermal/drivers/loongson2: Use bitfields and per-SoC thermal ops
This commit replaces open-coded masks and shifts with GENMASK() and FIELD_*
helpers, and defines named constants for the Loongson-2K2000. It also
splits the temperature read and thermal zone operations into SoC-specific
variants.
> diff --git a/drivers/thermal/loongson2_thermal.c b/drivers/thermal/loongson2_thermal.c
> index 45fe6100134ee..0660a74fd9222 100644
> --- a/drivers/thermal/loongson2_thermal.c
> +++ b/drivers/thermal/loongson2_thermal.c
[ ... ]
> @@ -64,71 +77,101 @@ static void loongson2_thermal_set_trip_temp(struct loongson2_thermal_data *data,
> data->chip_data->set_trips_regs(data, high, false, enable);
> }
>
> -static int loongson2_thermal_set_trips(struct thermal_zone_device *tz, int low, int high)
> +static int loognson2_thermal_set_trips(struct thermal_zone_device *tz, int low, int high)
[Severity: Low]
This isn't a bug, but is there a typo in this function name? It looks like
"loongson2" was accidentally misspelled as "loognson2" here.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790561983.git.zhoubinbin@loongson.cn?part=4
next prev parent reply other threads:[~2026-09-28 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 4:44 [PATCH v6 0/7] thermal: loongson2: Add support for Loongson-2K0300 SoC Binbin Zhou
2026-09-28 4:44 ` [PATCH v6 1/7] thermal/drivers/loongson2: Correct thermal sensor registration loop Binbin Zhou
2026-09-28 7:15 ` Daniel Lezcano
2026-09-28 8:17 ` Binbin Zhou
2026-09-28 13:23 ` Daniel Lezcano
2026-09-29 3:06 ` Binbin Zhou
2026-09-29 5:46 ` Daniel Lezcano
2026-09-29 8:23 ` Binbin Zhou
2026-09-29 8:43 ` Daniel Lezcano
2026-09-28 4:44 ` [PATCH v6 2/7] thermal/drivers/loongson2: Fix clamp() usage for thermal trip points Binbin Zhou
2026-09-28 4:44 ` [PATCH v6 3/7] thermal/drivers/loongson2: Fix Loongson-2K2000 trip point programming Binbin Zhou
2026-09-28 4:54 ` sashiko-bot
2026-09-28 4:44 ` [PATCH v6 4/7] thermal/drivers/loongson2: Use bitfields and per-SoC thermal ops Binbin Zhou
2026-09-28 4:52 ` sashiko-bot [this message]
2026-09-28 4:44 ` [PATCH v6 5/7] thermal/drivers/loongson2: Move per-SoC ops into chip data Binbin Zhou
2026-09-28 4:44 ` [PATCH v6 6/7] dt-bindings: thermal: loongson,ls2k-thermal: Add compatible for Loongson-2K0300 Binbin Zhou
2026-09-28 4:44 ` [PATCH v6 7/7] thermal/drivers/loongson2: Add Loongson-2K0300 support Binbin Zhou
2026-09-28 4:53 ` sashiko-bot
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=20260928045300.65DBF1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhoubinbin@loongson.cn \
/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