From: kernel test robot <lkp@intel.com>
To: jipinghuang <jipihuan@qti.qualcomm.com>,
rafael@kernel.org, daniel.lezcano@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
rui.zhang@intel.com, lukasz.luba@arm.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
jipinghuang <jipihuan@qti.qualcomm.com>
Subject: Re: [PATCH] Fixed a bug related to thermal framework boundary conditions: trip points do not need to be updated when polling is active, whereas they must be update to re-enable the irq when polling is inactive
Date: Mon, 27 Jul 2026 10:06:13 +0200 [thread overview]
Message-ID: <202607271050.J6ZhMOwT-lkp@intel.com> (raw)
In-Reply-To: <20260727035037.554303-1-jipihuan@qti.qualcomm.com>
Hi jipinghuang,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/thermal]
[also build test ERROR on linus/master v7.2-rc5 next-20260726]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/jipinghuang/Fixed-a-bug-related-to-thermal-framework-boundary-conditions-trip-points-do-not-need-to-be-updated-when-polling-is-activ/20260727-115235
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git thermal
patch link: https://lore.kernel.org/r/20260727035037.554303-1-jipihuan%40qti.qualcomm.com
patch subject: [PATCH] Fixed a bug related to thermal framework boundary conditions: trip points do not need to be updated when polling is active, whereas they must be update to re-enable the irq when polling is inactive
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260727/202607271050.J6ZhMOwT-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260727/202607271050.J6ZhMOwT-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607271050.J6ZhMOwT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/thermal/thermal_trip.c:64:83: error: use of undeclared identifier 'trip_temp'
64 | if (tz->prev_low_trip == low && tz->prev_high_trip == high && tz->temperature >= trip_temp)
| ^~~~~~~~~
1 error generated.
vim +/trip_temp +64 drivers/thermal/thermal_trip.c
53
54 void thermal_zone_set_trips(struct thermal_zone_device *tz, int low, int high)
55 {
56 int ret;
57
58 lockdep_assert_held(&tz->lock);
59
60 if (!tz->ops.set_trips)
61 return;
62
63 /* No need to change trip points */
> 64 if (tz->prev_low_trip == low && tz->prev_high_trip == high && tz->temperature >= trip_temp)
65 return;
66
67 tz->prev_low_trip = low;
68 tz->prev_high_trip = high;
69
70 dev_dbg(&tz->device,
71 "new temperature boundaries: %d < x < %d\n", low, high);
72
73 /*
74 * Set a temperature window. When this window is left the driver
75 * must inform the thermal core via thermal_zone_device_update.
76 */
77 ret = tz->ops.set_trips(tz, low, high);
78 if (ret)
79 dev_err(&tz->device, "Failed to set trips: %d\n", ret);
80 }
81
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-07-27 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:50 [PATCH] Fixed a bug related to thermal framework boundary conditions: trip points do not need to be updated when polling is active, whereas they must be update to re-enable the irq when polling is inactive jipinghuang
2026-07-27 8:06 ` kernel test robot [this message]
2026-07-27 8:57 ` kernel test robot
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=202607271050.J6ZhMOwT-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@kernel.org \
--cc=jipihuan@qti.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lukasz.luba@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/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