From: kernel test robot <lkp@intel.com>
To: victor.duicu@microchip.com, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, marius.cristea@microchip.com,
victor.duicu@microchip.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: temperature: add support for MCP998X
Date: Fri, 30 May 2025 12:39:46 +0800 [thread overview]
Message-ID: <202505301210.l4ZriiEX-lkp@intel.com> (raw)
In-Reply-To: <20250529093628.15042-3-victor.duicu@microchip.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0c86e33819785fe50616b6ee3fb35c1e4be406d5]
url: https://github.com/intel-lab-lkp/linux/commits/victor-duicu-microchip-com/dt-bindings-iio-temperature-add-support-for-MCP998X/20250529-173844
base: 0c86e33819785fe50616b6ee3fb35c1e4be406d5
patch link: https://lore.kernel.org/r/20250529093628.15042-3-victor.duicu%40microchip.com
patch subject: [PATCH v2 2/2] iio: temperature: add support for MCP998X
config: m68k-randconfig-r111-20250530 (https://download.01.org/0day-ci/archive/20250530/202505301210.l4ZriiEX-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.4.0
reproduce: (https://download.01.org/0day-ci/archive/20250530/202505301210.l4ZriiEX-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/202505301210.l4ZriiEX-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/temperature/mcp9982.c:200:14: sparse: sparse: symbol 'mcp9982_3db_values_map_tbl' was not declared. Should it be static?
vim +/mcp9982_3db_values_map_tbl +200 drivers/iio/temperature/mcp9982.c
199
> 200 unsigned int mcp9982_3db_values_map_tbl[11][3][2];
201 static const int mcp9982_sampl_fr[][2] = {
202 { 1, 16 },
203 { 1, 8 },
204 { 1, 4 },
205 { 1, 2 },
206 { 1, 1 },
207 { 2, 1 },
208 { 4, 1 },
209 { 8, 1 },
210 { 16, 1 },
211 { 32, 1 },
212 { 64, 1 },
213 };
214
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-30 4:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 9:36 [PATCH v2 0/2] add support for MCP998X victor.duicu
2025-05-29 9:36 ` [PATCH v2 1/2] dt-bindings: iio: temperature: " victor.duicu
2025-05-29 18:13 ` David Lechner
2025-05-30 15:55 ` Conor Dooley
2025-06-02 14:48 ` Victor.Duicu
2025-06-06 15:15 ` Conor Dooley
2025-06-10 13:29 ` Victor.Duicu
2025-06-10 15:17 ` Conor Dooley
2025-05-29 9:36 ` [PATCH v2 2/2] " victor.duicu
2025-05-29 18:36 ` Andy Shevchenko
2025-05-30 4:39 ` kernel test robot [this message]
2025-05-30 16:53 ` Jonathan Cameron
2025-06-02 14:49 ` Victor.Duicu
2025-06-07 17:28 ` Jonathan Cameron
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=202505301210.l4ZriiEX-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=nuno.sa@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=victor.duicu@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.