All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.com>
Subject: [linux-next:master 11921/12162] include/linux/nmi.h:160: undefined reference to `arch_trigger_cpumask_backtrace'
Date: Fri, 23 Jun 2023 23:21:36 +0800	[thread overview]
Message-ID: <202306232330.luFAk63S-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   8d2be868b42c08290509c60515865f4de24ea704
commit: 1141ba8fc84c333b138946d4cf973f5ade78b9ed [11921/12162] powerpc: move arch_trigger_cpumask_backtrace from nmi.h to irq.h
config: powerpc-randconfig-r025-20230622 (https://download.01.org/0day-ci/archive/20230623/202306232330.luFAk63S-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230623/202306232330.luFAk63S-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/202306232330.luFAk63S-lkp@intel.com/

All errors (new ones prefixed by >>):

   powerpc-linux-ld: kernel/panic.o: in function `trigger_all_cpu_backtrace':
>> include/linux/nmi.h:160: undefined reference to `arch_trigger_cpumask_backtrace'
>> powerpc-linux-ld: include/linux/nmi.h:160: undefined reference to `arch_trigger_cpumask_backtrace'
>> powerpc-linux-ld: include/linux/nmi.h:160: undefined reference to `arch_trigger_cpumask_backtrace'
   powerpc-linux-ld: kernel/sched/core.o: in function `trigger_single_cpu_backtrace':
   include/linux/nmi.h:178: undefined reference to `arch_trigger_cpumask_backtrace'
   powerpc-linux-ld: kernel/watchdog.o: in function `trigger_allbutself_cpu_backtrace':
   include/linux/nmi.h:166: undefined reference to `arch_trigger_cpumask_backtrace'
   powerpc-linux-ld: drivers/tty/sysrq.o:include/linux/nmi.h:160: more undefined references to `arch_trigger_cpumask_backtrace' follow


vim +160 include/linux/nmi.h

6e7458a6f074c7 Ulrich Obergfell 2014-10-13  151  
47cab6a722d44c Ingo Molnar      2009-08-03  152  /*
47cab6a722d44c Ingo Molnar      2009-08-03  153   * Create trigger_all_cpu_backtrace() out of the arch-provided
47cab6a722d44c Ingo Molnar      2009-08-03  154   * base function. Return whether such support was available,
47cab6a722d44c Ingo Molnar      2009-08-03  155   * to allow calling code to fall back to some other mechanism:
47cab6a722d44c Ingo Molnar      2009-08-03  156   */
9a01c3ed5cdb35 Chris Metcalf    2016-10-07  157  #ifdef arch_trigger_cpumask_backtrace
47cab6a722d44c Ingo Molnar      2009-08-03  158  static inline bool trigger_all_cpu_backtrace(void)
47cab6a722d44c Ingo Molnar      2009-08-03  159  {
9a01c3ed5cdb35 Chris Metcalf    2016-10-07 @160  	arch_trigger_cpumask_backtrace(cpu_online_mask, false);
47cab6a722d44c Ingo Molnar      2009-08-03  161  	return true;
47cab6a722d44c Ingo Molnar      2009-08-03  162  }
9a01c3ed5cdb35 Chris Metcalf    2016-10-07  163  

:::::: The code at line 160 was first introduced by commit
:::::: 9a01c3ed5cdb35d9004eb92510ee6ea11b4a5f16 nmi_backtrace: add more trigger_*_cpu_backtrace() methods

:::::: TO: Chris Metcalf <cmetcalf@mellanox.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2023-06-23 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 15:21 kernel test robot [this message]
2023-06-23 15:25 ` [linux-next:master 11921/12162] include/linux/nmi.h:160: undefined reference to `arch_trigger_cpumask_backtrace' Doug Anderson

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=202306232330.luFAk63S-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dianders@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pmladek@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.