Hi Jinyu, kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master] [also build test WARNING on rostedt-trace/for-next v6.6-rc5 next-20231010] [cannot apply to rostedt-trace/for-next-urgent] [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/Jinyu-Tang/Ftrace-make-sched_wakeup-can-focus-on-the-target-process/20231009-234127 base: linus/master patch link: https://lore.kernel.org/r/20231009153714.10743-1-tangjinyu%40tinylab.org patch subject: [PATCH v1] Ftrace: make sched_wakeup can focus on the target process config: i386-randconfig-062-20231010 (https://download.01.org/0day-ci/archive/20231011/202310110813.fxuatrh0-...@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231011/202310110813.fxuatrh0-...@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 <l...@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202310110813.fxuatrh0-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> kernel/trace/trace_sched_wakeup.c:368:1: sparse: sparse: symbol >> 'sched_wakeup_mutex' was not declared. Should it be static? -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki