From: Doug Anderson <dianders@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-nonmm-unstable 69/70] panic.c:undefined reference to `arch_trigger_cpumask_backtrace'
Date: Thu, 22 Jun 2023 19:42:04 -0700 [thread overview]
Message-ID: <CAD=FV=VqnC8o_Bsx8GWYNbp+mRb2kGdfkucy2+RV4tyyGBjK1A@mail.gmail.com> (raw)
In-Reply-To: <202306230940.cAAzoBuj-lkp@intel.com>
Hi,
On Thu, Jun 22, 2023 at 6:27 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> head: 2f300c1db6849096050b341817208f97d55586b9
> commit: 7cf0441a9e57e752c39bb70ceb2e74bbf66ec958 [69/70] powerpc: move arch_trigger_cpumask_backtrace from nmi.h to irq.h
> config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20230623/202306230940.cAAzoBuj-lkp@intel.com/config)
> compiler: powerpc-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230623/202306230940.cAAzoBuj-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/202306230940.cAAzoBuj-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> powerpc-linux-ld: kernel/panic.o: in function `panic':
> >> panic.c:(.text+0xa9c): undefined reference to `arch_trigger_cpumask_backtrace'
> >> powerpc-linux-ld: panic.c:(.text+0xae0): undefined reference to `arch_trigger_cpumask_backtrace'
> powerpc-linux-ld: kernel/panic.o: in function `oops_enter':
> panic.c:(.text+0x1518): undefined reference to `arch_trigger_cpumask_backtrace'
> powerpc-linux-ld: kernel/sched/core.o: in function `dump_cpu_task':
> >> core.c:(.text+0x1dd70): undefined reference to `arch_trigger_cpumask_backtrace'
> powerpc-linux-ld: kernel/hung_task.o: in function `check_hung_uninterruptible_tasks':
> >> hung_task.c:(.text+0x11e0): undefined reference to `arch_trigger_cpumask_backtrace'
> powerpc-linux-ld: kernel/watchdog.o:watchdog.c:(.text+0x8f0): more undefined references to `arch_trigger_cpumask_backtrace' follow
Argh. Since this is in Andrew's unstable, I'll send a v2 of my patch right away.
-Doug
prev parent reply other threads:[~2023-06-23 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 1:27 kernel test robot
2023-06-23 2:42 ` Doug Anderson [this message]
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='CAD=FV=VqnC8o_Bsx8GWYNbp+mRb2kGdfkucy2+RV4tyyGBjK1A@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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