From: kernel test robot <lkp@intel.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jcmvbkbc-xtensa:xtensa-6.13-esp32 35/53] drivers/misc/esp32-ipc.c:228:34: warning: unused variable 'esp32_ipc_match'
Date: Tue, 4 Feb 2025 00:56:35 +0800 [thread overview]
Message-ID: <202502040003.WRLTz6Ya-lkp@intel.com> (raw)
Hi Max,
First bad commit (maybe != root cause):
tree: https://github.com/jcmvbkbc/linux-xtensa xtensa-6.13-esp32
head: f4a6cef2509c4e81637b6d5d6f0c27966895985a
commit: 08b8a525de25b35564cb9ae5f7b5ad1122a84fed [35/53] esp_wifi: add IPC transport
config: mips-jazz_defconfig (https://download.01.org/0day-ci/archive/20250204/202502040003.WRLTz6Ya-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 355d0b186f178668b103068537e517f3d52ad639)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250204/202502040003.WRLTz6Ya-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/202502040003.WRLTz6Ya-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/misc/esp32-ipc.c:228:34: warning: unused variable 'esp32_ipc_match' [-Wunused-const-variable]
228 | static const struct of_device_id esp32_ipc_match[] = {
| ^~~~~~~~~~~~~~~
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for ESP32_IPC
Depends on [n]: OF [=n] && HAS_IOMEM [=y]
Selected by [y]:
- ESP32_WIFI_SHMEM [=y] && NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ESPRESSIF [=y]
vim +/esp32_ipc_match +228 drivers/misc/esp32-ipc.c
ff5d67ac76ee59 Max Filippov 2023-08-11 227
ff5d67ac76ee59 Max Filippov 2023-08-11 @228 static const struct of_device_id esp32_ipc_match[] = {
ff5d67ac76ee59 Max Filippov 2023-08-11 229 {
ff5d67ac76ee59 Max Filippov 2023-08-11 230 .compatible = "esp,esp32-ipc",
ff5d67ac76ee59 Max Filippov 2023-08-11 231 }, {},
ff5d67ac76ee59 Max Filippov 2023-08-11 232 };
ff5d67ac76ee59 Max Filippov 2023-08-11 233 MODULE_DEVICE_TABLE(of, esp32_ipc_match);
ff5d67ac76ee59 Max Filippov 2023-08-11 234
:::::: The code at line 228 was first introduced by commit
:::::: ff5d67ac76ee59b6351fd6f70df8d0178ef4f72a misc/esp32-ipc: introduce generic IPC for ESP32
:::::: TO: Max Filippov <jcmvbkbc@gmail.com>
:::::: CC: Max Filippov <jcmvbkbc@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-03 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502040003.WRLTz6Ya-lkp@intel.com \
--to=lkp@intel.com \
--cc=jcmvbkbc@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 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.