From: kernel test robot <lkp@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: arch/powerpc/kernel/time.c:169:29: error: unused function 'read_spurr'
Date: Sat, 12 Aug 2023 11:59:55 +0800 [thread overview]
Message-ID: <202308121120.u2d3YPVt-lkp@intel.com> (raw)
Hi Nathan,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 190bf7b14b0cf3df19c059061be032bd8994a597
commit: 015d98149b326e0f1f02e44413112ca8b4330543 powerpc/barrier: Avoid collision with clang's __lwsync macro
date: 2 years, 2 months ago
config: powerpc-randconfig-r011-20230812 (https://download.01.org/0day-ci/archive/20230812/202308121120.u2d3YPVt-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308121120.u2d3YPVt-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/202308121120.u2d3YPVt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/powerpc/kernel/time.c:169:29: error: unused function 'read_spurr' [-Werror,-Wunused-function]
169 | static inline unsigned long read_spurr(unsigned long tb)
| ^
1 error generated.
--
>> arch/powerpc/sysdev/grackle.c:26:20: error: unused function 'grackle_set_stg' [-Werror,-Wunused-function]
26 | static inline void grackle_set_stg(struct pci_controller* bp, int enable)
| ^
1 error generated.
vim +/read_spurr +169 arch/powerpc/kernel/time.c
c6622f63db86fc Paul Mackerras 2006-02-24 164
c6622f63db86fc Paul Mackerras 2006-02-24 165 /*
cf9efce0ce3136 Paul Mackerras 2010-08-26 166 * Read the SPURR on systems that have it, otherwise the PURR,
cf9efce0ce3136 Paul Mackerras 2010-08-26 167 * or if that doesn't exist return the timebase value passed in.
c6622f63db86fc Paul Mackerras 2006-02-24 168 */
abcff86df2d2ec Christophe Leroy 2018-08-02 @169 static inline unsigned long read_spurr(unsigned long tb)
c6622f63db86fc Paul Mackerras 2006-02-24 170 {
cf9efce0ce3136 Paul Mackerras 2010-08-26 171 if (cpu_has_feature(CPU_FTR_SPURR))
cf9efce0ce3136 Paul Mackerras 2010-08-26 172 return mfspr(SPRN_SPURR);
c6622f63db86fc Paul Mackerras 2006-02-24 173 if (cpu_has_feature(CPU_FTR_PURR))
c6622f63db86fc Paul Mackerras 2006-02-24 174 return mfspr(SPRN_PURR);
cf9efce0ce3136 Paul Mackerras 2010-08-26 175 return tb;
c6622f63db86fc Paul Mackerras 2006-02-24 176 }
c6622f63db86fc Paul Mackerras 2006-02-24 177
:::::: The code at line 169 was first introduced by commit
:::::: abcff86df2d2ec0a0ca9470fa5d2a184af18928a powerpc/time: Only set CONFIG_ARCH_HAS_SCALED_CPUTIME on PPC64
:::::: TO: Christophe Leroy <christophe.leroy@c-s.fr>
:::::: CC: Michael Ellerman <mpe@ellerman.id.au>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-12 4:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202308121120.u2d3YPVt-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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
all inboxes | Powered by JetHome®