From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 1576/1892] s390-linux-ld: kexec.c:undefined reference to `crashk_low_res'
Date: Mon, 29 Jan 2024 22:55:35 +0800 [thread overview]
Message-ID: <Zbe8Z/h1oKu/yncB@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202401261933.gyy8YHnT-lkp@intel.com>
On 01/26/24 at 07:45pm, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 01af33cc9894b4489fb68fa35c40e9fe85df63dc
> commit: ad82e944d12ca472df041acb4c732bd630a81b90 [1576/1892] s390, crash: wrap crash dumping code into crash related ifdefs
> config: s390-randconfig-r131-20230823 (https://download.01.org/0day-ci/archive/20240126/202401261933.gyy8YHnT-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240126/202401261933.gyy8YHnT-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/202401261933.gyy8YHnT-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> s390-linux-ld: arch/s390/kernel/machine_kexec.o: in function `arch_crash_save_vmcoreinfo':
> machine_kexec.c:(.text+0x274): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: machine_kexec.c:(.text+0x28c): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: machine_kexec.c:(.text+0x2a2): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: machine_kexec.c:(.text+0x2c4): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: machine_kexec.c:(.text+0x2e6): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.o:machine_kexec.c:(.text+0x308): more undefined references to `vmcoreinfo_append_str' follow
> s390-linux-ld: arch/s390/kernel/machine_kexec.o: in function `arch_crash_save_vmcoreinfo':
> machine_kexec.c:(.text+0x340): undefined reference to `paddr_vmcoreinfo_note'
> s390-linux-ld: drivers/of/kexec.o: in function `of_kexec_alloc_and_setup_fdt':
> kexec.c:(.text+0x60c): undefined reference to `crashk_res'
> >> s390-linux-ld: kexec.c:(.text+0x660): undefined reference to `crashk_low_res'
Sorry for late response. These have been fixed in below patches.
[PATCH linux-next 3/3] arch, crash: move arch_crash_save_vmcoreinfo() out to file vmcore_info.c
https://lore.kernel.org/all/20240129135033.157195-3-bhe@redhat.com/T/#u
[PATCH linux-next 2/3] crash: fix building error in generic codes
https://lore.kernel.org/all/20240129135033.157195-2-bhe@redhat.com/T/#u
prev parent reply other threads:[~2024-01-29 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 11:45 [linux-next:master 1576/1892] s390-linux-ld: kexec.c:undefined reference to `crashk_low_res' kernel test robot
2024-01-29 14:55 ` Baoquan He [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=Zbe8Z/h1oKu/yncB@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--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 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.