From: kernel test robot <lkp@intel.com>
To: Anthony Iliopoulos <ailiop@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: <llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/profile: remove setup_profiling_timer
Date: Sun, 23 Aug 2026 21:23:30 +0800 [thread overview]
Message-ID: <202608231532.dENn2OSP-lkp@intel.com> (raw)
In-Reply-To: <20260821091744.91496-1-ailiop@suse.com>
Hi Anthony,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on linus/master v7.2 next-20260821]
[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/Anthony-Iliopoulos/kernel-profile-remove-setup_profiling_timer/20260821-111744
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20260821091744.91496-1-ailiop%40suse.com
patch subject: [PATCH] kernel/profile: remove setup_profiling_timer
config: loongarch-randconfig-001-20260823 (https://download.01.org/0day-ci/archive/20260823/202608231532.dENn2OSP-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 935bfc708590c60147a79c7df145bb6e68b1d388)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260823/202608231532.dENn2OSP-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/202608231532.dENn2OSP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/loongarch/kernel/smp.c:720:5: warning: no previous prototype for function 'setup_profiling_timer' [-Wmissing-prototypes]
720 | int setup_profiling_timer(unsigned int multiplier)
| ^
arch/loongarch/kernel/smp.c:720:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
720 | int setup_profiling_timer(unsigned int multiplier)
| ^
| static
1 warning generated.
vim +/setup_profiling_timer +720 arch/loongarch/kernel/smp.c
46859ac8af52ae Huacai Chen 2022-05-31 718
c718a0bad75cce Bibo Mao 2023-09-20 719 #ifdef CONFIG_PROFILING
46859ac8af52ae Huacai Chen 2022-05-31 @720 int setup_profiling_timer(unsigned int multiplier)
46859ac8af52ae Huacai Chen 2022-05-31 721 {
46859ac8af52ae Huacai Chen 2022-05-31 722 return 0;
46859ac8af52ae Huacai Chen 2022-05-31 723 }
c718a0bad75cce Bibo Mao 2023-09-20 724 #endif
46859ac8af52ae Huacai Chen 2022-05-31 725
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-08-23 13:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260821091744.91496-1-ailiop@suse.com>]
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=202608231532.dENn2OSP-lkp@intel.com \
--to=lkp@intel.com \
--cc=ailiop@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox