From: kernel test robot <lkp@intel.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, tsahu@linux.ibm.com,
anshuman.khandual@arm.com, ssawgyw@gmail.com,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH -next] memblock: unify memblock dump and debugfs show
Date: Fri, 26 May 2023 19:09:03 +0800 [thread overview]
Message-ID: <202305261822.ZFRYZVQk-lkp@intel.com> (raw)
In-Reply-To: <20230525115856.124507-1-wangkefeng.wang@huawei.com>
Hi Kefeng,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20230525]
url: https://github.com/intel-lab-lkp/linux/commits/Kefeng-Wang/memblock-unify-memblock-dump-and-debugfs-show/20230525-194341
base: next-20230525
patch link: https://lore.kernel.org/r/20230525115856.124507-1-wangkefeng.wang%40huawei.com
patch subject: [PATCH -next] memblock: unify memblock dump and debugfs show
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20230526/202305261822.ZFRYZVQk-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/08ce8490dec830c059127709a3a692ac7368287e
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Kefeng-Wang/memblock-unify-memblock-dump-and-debugfs-show/20230525-194341
git checkout 08ce8490dec830c059127709a3a692ac7368287e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 ~/bin/make.cross W=1 O=build_dir ARCH=arc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 ~/bin/make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305261822.ZFRYZVQk-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/memblock.c: In function 'memblock_dump.constprop':
>> mm/memblock.c:1910:27: error: 'flagname' causes a section type conflict with 'memblock_debug'
1910 | static const char * const flagname[] __initdata_memblock = {
| ^~~~~~~~
mm/memblock.c:158:12: note: 'memblock_debug' was declared here
158 | static int memblock_debug __initdata_memblock;
| ^~~~~~~~~~~~~~
vim +1910 mm/memblock.c
1909
> 1910 static const char * const flagname[] __initdata_memblock = {
1911 [ilog2(MEMBLOCK_HOTPLUG)] = "HOTPLUG",
1912 [ilog2(MEMBLOCK_MIRROR)] = "MIRROR",
1913 [ilog2(MEMBLOCK_NOMAP)] = "NOMAP",
1914 [ilog2(MEMBLOCK_DRIVER_MANAGED)] = "DRV_MNG",
1915 [ilog2(MEMBLOCK_MAX_UNKNOWN)] = "UNKNOWN",
1916 };
1917
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-05-26 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 11:58 [PATCH -next] memblock: unify memblock dump and debugfs show Kefeng Wang
2023-05-26 2:57 ` kernel test robot
2023-05-26 11:09 ` kernel test robot [this message]
2023-05-26 11:40 ` Kefeng Wang
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=202305261822.ZFRYZVQk-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=ssawgyw@gmail.com \
--cc=tsahu@linux.ibm.com \
--cc=wangkefeng.wang@huawei.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.