From: kernel test robot <lkp@intel.com>
To: Sergio Melas <sergiomelas@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>, Rong Zhang <i@rong.moe>
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Armin Wolf <W_Armin@gmx.de>,
"Derek J . Clark" <derekjohn.clark@gmail.com>,
Sergio Melas <sergiomelas@gmail.com>
Subject: Re: [PATCH v1] hwmon: (yogafan) Massive hardware expansion and structural refactoring
Date: Thu, 30 Apr 2026 00:27:07 +0200 [thread overview]
Message-ID: <202604300021.hu1KkNxy-lkp@intel.com> (raw)
In-Reply-To: <20260413060931.31091-2-sergiomelas@gmail.com>
Hi Sergio,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on linus/master v7.1-rc1 next-20260429]
[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/Sergio-Melas/hwmon-yogafan-Massive-hardware-expansion-and-structural-refactoring/20260417-063319
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link: https://lore.kernel.org/r/20260413060931.31091-2-sergiomelas%40gmail.com
patch subject: [PATCH v1] hwmon: (yogafan) Massive hardware expansion and structural refactoring
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260430/202604300021.hu1KkNxy-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/202604300021.hu1KkNxy-lkp@intel.com/
All warnings (new ones prefixed by >>):
Runtime Survivability
===================== [docutils]
Documentation/hwmon/yogafan.rst:165: ERROR: Unexpected indentation. [docutils]
>> Documentation/hwmon/yogafan.rst:166: WARNING: Bullet list ends without a blank line; unexpected unindent. [docutils]
Documentation/hwmon/yogafan.rst:169: ERROR: Unexpected indentation. [docutils]
>> Documentation/hwmon/yogafan.rst:170: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/hwmon/yogafan.rst:171: WARNING: Bullet list ends without a blank line; unexpected unindent. [docutils]
Documentation/hwmon/yogafan.rst:318: ERROR: Malformed table.
Bottom border or header rule does not match top border.
vim +166 Documentation/hwmon/yogafan.rst
162
163 This approach ensures that the RLLag filter is a passive discrete-time
164 first-order lag model:
165 - **Smoothing:** Low-resolution step increments are smoothed into 1-RPM
> 166 increments.
167 - **Slew-Rate Limiting:** Prevents unrealistic readings by capping the
168 change
169 to 1500 RPM/s, matching physical fan inertia.
> 170 - **Polling Independence:** The filter math scales based on the time
171 delta between userspace reads, ensuring a consistent physical curve
172 regardless of polling frequency.
173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-29 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:09 [PATCH v1] hwmon: (yogafan) Massive hardware expansion and structural refactoring Sergio Melas
2026-04-13 6:38 ` sashiko-bot
2026-04-13 13:51 ` Guenter Roeck
2026-04-13 13:55 ` Guenter Roeck
2026-04-17 21:37 ` kernel test robot
2026-04-18 10:31 ` Rong Zhang
2026-04-18 11:23 ` Rong Zhang
2026-04-18 13:49 ` Guenter Roeck
2026-04-18 15:14 ` Rong Zhang
2026-04-18 15:49 ` Guenter Roeck
2026-04-29 22:27 ` kernel test robot [this message]
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=202604300021.hu1KkNxy-lkp@intel.com \
--to=lkp@intel.com \
--cc=W_Armin@gmx.de \
--cc=derekjohn.clark@gmail.com \
--cc=i@rong.moe \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sergiomelas@gmail.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