Hi Kartik, kernel test robot noticed the following build warnings:
[auto build test WARNING on tegra/for-next] [also build test WARNING on kees/for-next/hardening akpm-mm/mm-everything linus/master v6.6-rc5 next-20231012] [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/Kartik/mm-util-Introduce-kmemdup_array-to-duplicate-an-array/20231011-192039 base: https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next patch link: https://lore.kernel.org/r/20231011093412.7994-8-kkartik%40nvidia.com patch subject: [PATCH v4 7/8] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234 config: arm64-randconfig-002-20231012 (https://download.01.org/0day-ci/archive/20231013/[email protected]/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/[email protected]/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 <[email protected]> | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/ All warnings (new ones prefixed by >>): >> drivers/soc/tegra/fuse/fuse-tegra.c:314:36: warning: 'tegra_fuse_acpi_match' >> defined but not used [-Wunused-const-variable=] 314 | static const struct acpi_device_id tegra_fuse_acpi_match[] = { | ^~~~~~~~~~~~~~~~~~~~~ vim +/tegra_fuse_acpi_match +314 drivers/soc/tegra/fuse/fuse-tegra.c 313 > 314 static const struct acpi_device_id tegra_fuse_acpi_match[] = { 315 { "NVDA200F" }, 316 { /* sentinel */ } 317 }; 318 MODULE_DEVICE_TABLE(acpi, tegra_fuse_acpi_match); 319 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
