From: kernel test robot <lkp@intel.com>
To: Shakeel Butt <shakeelb@google.com>, Roman Gushchin <guro@fb.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@lists.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Shakeel Butt <shakeelb@google.com>
Subject: Re: [PATCH v2] mm: memcontrol: account pagetables per node
Date: Tue, 24 Nov 2020 07:47:48 +0800 [thread overview]
Message-ID: <202011240741.3ZEEC8Zd-lkp@intel.com> (raw)
In-Reply-To: <20201123161425.341314-1-shakeelb@google.com>
[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]
Hi Shakeel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on m68k/for-next]
[also build test ERROR on driver-core/driver-core-testing linus/master v5.10-rc5 next-20201123]
[cannot apply to mmotm/master cgroup/for-next hnaz-linux-mm/master]
[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/Shakeel-Butt/mm-memcontrol-account-pagetables-per-node/20201124-001640
base: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-next
config: arm-keystone_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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/22c0e4c0c8b324b0a2ffb5e11b18ecb7cea1543d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Shakeel-Butt/mm-memcontrol-account-pagetables-per-node/20201124-001640
git checkout 22c0e4c0c8b324b0a2ffb5e11b18ecb7cea1543d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: arch/arm/mm/idmap.o: in function `init_static_idmap':
>> idmap.c:(.init.text+0x10c): undefined reference to `inc_lruvec_page_state'
arm-linux-gnueabi-ld: arch/arm/mm/pgd.o: in function `pgd_alloc':
pgd.c:(.text+0x32c): undefined reference to `dec_lruvec_page_state'
arm-linux-gnueabi-ld: arch/arm/mm/pgd.o: in function `pgd_free':
pgd.c:(.text+0x4c8): undefined reference to `dec_lruvec_page_state'
>> arm-linux-gnueabi-ld: pgd.c:(.text+0x544): undefined reference to `dec_lruvec_page_state'
arm-linux-gnueabi-ld: pgd.c:(.text+0x634): undefined reference to `dec_lruvec_page_state'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24565 bytes --]
prev parent reply other threads:[~2020-11-23 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 16:14 [PATCH v2] mm: memcontrol: account pagetables per node Shakeel Butt
2020-11-23 21:42 ` kernel test robot
2020-11-23 23:47 ` kernel test robot [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=202011240741.3ZEEC8Zd-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeelb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).