Devicetree
 help / color / mirror / Atom feed
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 v9 2/7] thermal/drivers/loongson2: Fix clamp() usage for thermal trip points
Date: Mon, 09 Nov 2026 08:15:16 +0000	[thread overview]
Message-ID: <sashiko-outbox-204576@kernel.org> (raw)
In-Reply-To: <7ae230bbff1143978c90f1566bfca6d17101929c.1794211535.git.zhoubinbin@loongson.cn>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] thermal/drivers/loongson2: incorrect Fixes tag in
  loongson2_thermal_set()
--

commit 7c662ff635bdb14cac997976404a99f9d5a1e734
Author: Binbin Zhou <zhoubinbin@loongson.cn>

> thermal/drivers/loongson2: Fix clamp() usage for thermal trip points
>
> clamp() takes the value to clamp as its first argument, followed by the
> minimum and maximum bounds. The current code passes the -40 and 125
> limits as the value instead, so the trip thresholds are not clamped to the
> supported sensor range.
>
> Correct the arguments so that low and high are clamped to [-40, 125].
>
> Cc: stable@vger.kernel.org
> Fixes: 734b5def91b5 ("thermal/drivers/loongson2: Add Loongson-2K2000 support")
> Reviewed-by: Huacai Chen <chenhuacai@loongson.cn>
> Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>

[Severity: Low]
Should the Fixes tag reference e7e3a7c35791 ("thermal/drivers/loongson-2: Add
thermal management support") instead?  Commit 734b5def91b5 ("thermal/drivers/loongson2:
Add Loongson-2K2000 support") did not modify loongson2_thermal_set(), whereas
the inverted clamp() arguments were introduced in e7e3a7c35791 ("thermal/drivers/loongson-2:
Add thermal management support") and later moved into loongson2_set_ctrl_regs()
calls in 6ef6d5ff5edd ("thermal/drivers/loongson2: Trivial code style
adjustment").

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794211535.git.zhoubinbin@loongson.cn?part=2

  reply	other threads:[~2026-11-09  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  8:08 [PATCH v9 0/7] thermal/drivers/loongson2: Fix trip programming and add Loongson-2K0300 support Binbin Zhou
2026-11-09  8:08 ` [PATCH v9 1/7] thermal/drivers/loongson2: Fix negative trip conversion in set_trips Binbin Zhou
2026-11-09  8:08 ` [PATCH v9 2/7] thermal/drivers/loongson2: Fix clamp() usage for thermal trip points Binbin Zhou
2026-11-09  8:15   ` sashiko-bot [this message]
2026-11-09  8:08 ` [PATCH v9 3/7] thermal/drivers/loongson2: Fix Loongson-2K2000 trip point programming Binbin Zhou
2026-11-09  8:09 ` [PATCH v9 4/7] thermal/drivers/loongson2: Simplify thermal sensor registration Binbin Zhou
2026-11-09  8:09 ` [PATCH v9 5/7] thermal/drivers/loongson2: Move per-SoC ops and init into chip data Binbin Zhou
2026-11-09  8:09 ` [PATCH v9 6/7] dt-bindings: thermal: loongson,ls2k-thermal: Add compatible for Loongson-2K0300 Binbin Zhou
2026-11-09  8:18   ` sashiko-bot
2026-11-09  8:10 ` [PATCH v9 7/7] thermal/drivers/loongson2: Add Loongson-2K0300 support Binbin Zhou
2026-11-09  8:32   ` 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=sashiko-outbox-204576@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