Hi Cao, kernel test robot noticed the following build warnings:
[auto build test WARNING on trace/for-next] [also build test WARNING on linus/master v7.0 next-20260414] [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/Cao-Ruichuang/ring-buffer-Preserve-true-payload-lengths-in-long-data-events/20260415-040554 base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next patch link: https://lore.kernel.org/r/20260407091550.67963-1-create0818%40163.com patch subject: [PATCH] ring-buffer: Preserve true payload lengths in long data events config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260415/[email protected]/config) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/[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 >>): >> Warning: kernel/trace/ring_buffer.c:4786 function parameter 'force_long' not >> described in '__ring_buffer_lock_reserve' >> Warning: kernel/trace/ring_buffer.c:4786 expecting prototype for >> ring_buffer_lock_reserve(). Prototype was for __ring_buffer_lock_reserve() >> instead -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
