From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] arch: arm64: have memblocks out of kernel text use section map
Date: Sat, 13 Nov 2021 10:09:53 +0800 [thread overview]
Message-ID: <202111131031.JsLTnir0-lkp@intel.com> (raw)
In-Reply-To: <1636708842-25787-1-git-send-email-huangzhaoyang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]
Hi Huangzhaoyang,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on v5.15 next-20211112]
[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]
url: https://github.com/0day-ci/linux/commits/Huangzhaoyang/arch-arm64-have-memblocks-out-of-kernel-text-use-section-map/20211112-172142
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/1e24a50ddba38b8bed8d75bc2b788da88b354522
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Huangzhaoyang/arch-arm64-have-memblocks-out-of-kernel-text-use-section-map/20211112-172142
git checkout 1e24a50ddba38b8bed8d75bc2b788da88b354522
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux.o(.text+0x22878): Section mismatch in reference from the function alloc_init_cont_pmd() to the variable .init.data:crash_mem_map
The function alloc_init_cont_pmd() references
the variable __initdata crash_mem_map.
This is often because alloc_init_cont_pmd lacks a __initdata
annotation or the annotation of crash_mem_map is wrong.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 55900 bytes --]
next prev parent reply other threads:[~2021-11-13 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 9:20 [RFC PATCH] arch: arm64: have memblocks out of kernel text use section map Huangzhaoyang
2021-11-12 9:31 ` Ard Biesheuvel
2021-11-12 9:45 ` Zhaoyang Huang
2021-11-13 2:09 ` kernel test robot [this message]
2021-11-21 9:44 ` kernel test robot
2021-11-21 9:44 ` kernel test robot
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=202111131031.JsLTnir0-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.