[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202501121203.Kw9SnPYP-lkp@intel.com>
Date: Sun, 12 Jan 2025 12:52:22 +0800
From: kernel test robot <lkp@...el.com>
To: Markus Burri <markus.burri@...com>, linux-kernel@...r.kernel.org
Cc: oe-kbuild-all@...ts.linux.dev, Markus Burri <markus.burri@...com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Marek Vasut <marex@...x.de>,
linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
Manuel Traut <manuel.traut@...com>
Subject: Re: [PATCH v1 3/7] rtc-rv8803: add register definitions for rv8901
tamper detection
Hi Markus,
kernel test robot noticed the following build warnings:
[auto build test WARNING on abelloni/rtc-next]
[also build test WARNING on robh/for-next linus/master v6.13-rc6 next-20250110]
[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/Markus-Burri/dt-bindings-rtc-add-new-type-for-epson-rx8901/20250110-141934
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
patch link: https://lore.kernel.org/r/20250110061401.358371-4-markus.burri%40mt.com
patch subject: [PATCH v1 3/7] rtc-rv8803: add register definitions for rv8901 tamper detection
config: m68k-randconfig-r122-20250111 (https://download.01.org/0day-ci/archive/20250112/202501121203.Kw9SnPYP-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250112/202501121203.Kw9SnPYP-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501121203.Kw9SnPYP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/rtc/rtc-rv8803.c:141:26: sparse: sparse: symbol 'pull_resistor_txt' was not declared. Should it be static?
>> drivers/rtc/rtc-rv8803.c:153:26: sparse: sparse: symbol 'trigger_txt' was not declared. Should it be static?
>> drivers/rtc/rtc-rv8803.c:161:26: sparse: sparse: symbol 'buffer_mode_txt' was not declared. Should it be static?
>> drivers/rtc/rtc-rv8803.c:167:26: sparse: sparse: symbol 'trg_status_txt' was not declared. Should it be static?
vim +/pull_resistor_txt +141 drivers/rtc/rtc-rv8803.c
140
> 141 const struct cfg_val_txt pull_resistor_txt[] = {
142 { "no", no },
143 { "PU/500k", pull_up_500k },
144 { "PU/1M", pull_up_1M },
145 { "PU/10M", pull_up_10M },
146 { "PD/500k", pull_down_500k },
147 { "no", 0b101, 1 },
148 { "no", 0b110, 1 },
149 { "no", 0b111, 1 },
150 { NULL }
151 };
152
> 153 const struct cfg_val_txt trigger_txt[] = {
154 { "falling", falling_edge },
155 { "rising", rising_edge },
156 { "both", both_edges },
157 { "both", 0b11, 1 },
158 { NULL }
159 };
160
> 161 const struct cfg_val_txt buffer_mode_txt[] = {
162 { "inhibit", inhibit },
163 { "overwrite", overwrite },
164 { NULL }
165 };
166
> 167 const struct cfg_val_txt trg_status_txt[] = {
168 { "EVIN1", BIT(5) },
169 { "EVIN2", BIT(6) },
170 { "EVIN3", BIT(7) },
171 { "CMD", BIT(4) },
172 { "VBATL", BIT(3) },
173 { "VTMPL", BIT(2) },
174 { "VDDL", BIT(1) },
175 { "OSCSTP", BIT(0) },
176 { NULL }
177 };
178
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists