Hi Michael, kernel test robot noticed the following build warnings: [auto build test WARNING on 052d534373b7ed33712a63d5e17b2b6cdbce84fd] url: https://github.com/intel-lab-lkp/linux/commits/Michael-Grzeschik/usb-gadget-function-9pfs/20240116-095914 base: 052d534373b7ed33712a63d5e17b2b6cdbce84fd patch link: https://lore.kernel.org/r/20240116-ml-topic-u9p-v1-1-ad8c306f9a4e%40pengutronix.de patch subject: [PATCH 1/3] usb: gadget: function: 9pfs config: microblaze-randconfig-r132-20240117 (https://download.01.org/0day-ci/archive/20240117/202401170734.7rHBG2LF-lkp@xxxxxxxxx/config) compiler: microblaze-linux-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20240117/202401170734.7rHBG2LF-lkp@xxxxxxxxx/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@xxxxxxxxx> | Closes: https://lore.kernel.org/oe-kbuild-all/202401170734.7rHBG2LF-lkp@xxxxxxxxx/ sparse warnings: (new ones prefixed by >>) >> drivers/usb/gadget/function/f_9pfs.c:825:12: sparse: sparse: symbol 'usb9pfs_modinit' was not declared. Should it be static? >> drivers/usb/gadget/function/f_9pfs.c:838:13: sparse: sparse: symbol 'usb9pfs_modexit' was not declared. Should it be static? vim +/usb9pfs_modinit +825 drivers/usb/gadget/function/f_9pfs.c 824 > 825 int __init usb9pfs_modinit(void) 826 { 827 int ret; 828 829 INIT_LIST_HEAD(&usbg_function_list); 830 831 ret = usb_function_register(&usb9pfsusb_func); 832 if (!ret) 833 v9fs_register_trans(&p9_usbg_trans); 834 835 return ret; 836 } 837 > 838 void __exit usb9pfs_modexit(void) 839 { 840 usb_function_unregister(&usb9pfsusb_func); 841 v9fs_unregister_trans(&p9_usbg_trans); 842 } 843 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
