From: kernel test robot <lkp@intel.com>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4365/10347] drivers/net/dsa/microchip/ksz_spi.c:132:34: warning: unused variable 'ksz_dt_ids'
Date: Thu, 14 Jul 2022 14:16:40 +0800 [thread overview]
Message-ID: <202207141406.IF2aPRxC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4662b7adea50bb62e993a67f611f3be625d3df0d
commit: 4658f2fe8fbcb12c1db0577ad9c46b67f10d09f1 [4365/10347] net: dsa: microchip: common ksz_spi_probe for ksz switches
config: hexagon-randconfig-r023-20220714 (https://download.01.org/0day-ci/archive/20220714/202207141406.IF2aPRxC-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 5e61b9c556267086ef9b743a0b57df302eef831b)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4658f2fe8fbcb12c1db0577ad9c46b67f10d09f1
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 4658f2fe8fbcb12c1db0577ad9c46b67f10d09f1
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/net/dsa/microchip/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/net/dsa/microchip/ksz_spi.c:132:34: warning: unused variable 'ksz_dt_ids' [-Wunused-const-variable]
static const struct of_device_id ksz_dt_ids[] = {
^
1 warning generated.
vim +/ksz_dt_ids +132 drivers/net/dsa/microchip/ksz_spi.c
131
> 132 static const struct of_device_id ksz_dt_ids[] = {
133 {
134 .compatible = "microchip,ksz8765",
135 .data = &ksz_switch_chips[KSZ8765]
136 },
137 {
138 .compatible = "microchip,ksz8794",
139 .data = &ksz_switch_chips[KSZ8794]
140 },
141 {
142 .compatible = "microchip,ksz8795",
143 .data = &ksz_switch_chips[KSZ8795]
144 },
145 {
146 .compatible = "microchip,ksz8863",
147 .data = &ksz_switch_chips[KSZ8830]
148 },
149 {
150 .compatible = "microchip,ksz8873",
151 .data = &ksz_switch_chips[KSZ8830]
152 },
153 {
154 .compatible = "microchip,ksz9477",
155 .data = &ksz_switch_chips[KSZ9477]
156 },
157 {
158 .compatible = "microchip,ksz9897",
159 .data = &ksz_switch_chips[KSZ9897]
160 },
161 {
162 .compatible = "microchip,ksz9893",
163 .data = &ksz_switch_chips[KSZ9893]
164 },
165 {
166 .compatible = "microchip,ksz9563",
167 .data = &ksz_switch_chips[KSZ9893]
168 },
169 {
170 .compatible = "microchip,ksz8563",
171 .data = &ksz_switch_chips[KSZ9893]
172 },
173 {
174 .compatible = "microchip,ksz9567",
175 .data = &ksz_switch_chips[KSZ9567]
176 },
177 {},
178 };
179 MODULE_DEVICE_TABLE(of, ksz_dt_ids);
180
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-14 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 6:16 kernel test robot [this message]
2022-07-14 8:21 ` Arnd Bergmann
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=202207141406.IF2aPRxC-lkp@intel.com \
--to=lkp@intel.com \
--cc=arun.ramadoss@microchip.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
/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