From: kernel test robot <lkp@intel.com>
To: Wupeng Ma <mawupeng1@huawei.com>, akpm@linux-foundation.org
Cc: kbuild-all@lists.01.org, corbet@lwn.net, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.com,
songmuchun@bytedance.com, mike.kravetz@oracle.com,
osalvador@suse.de, surenb@google.com, mawupeng1@huawei.com,
rppt@kernel.org, charante@codeaurora.org, jsavitz@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
wangkefeng.wang@huawei.com
Subject: Re: [PATCH -next 2/2] mm: sysctl: Introduce per zone watermark_scale_factor
Date: Thu, 18 Aug 2022 19:49:10 +0800 [thread overview]
Message-ID: <202208181945.AoDDCp5a-lkp@intel.com> (raw)
In-Reply-To: <20220818090430.2859992-3-mawupeng1@huawei.com>
Hi Wupeng,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20220818]
url: https://github.com/intel-lab-lkp/linux/commits/Wupeng-Ma/watermark-related-improvement-on-zone-movable/20220818-170659
base: 5b6a4bf680d61b1dd26629840f848d0df8983c62
config: openrisc-buildonly-randconfig-r004-20220818 (https://download.01.org/0day-ci/archive/20220818/202208181945.AoDDCp5a-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.1.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/intel-lab-lkp/linux/commit/d126658752d146244ef366f63b8edbb797dc5436
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Wupeng-Ma/watermark-related-improvement-on-zone-movable/20220818-170659
git checkout d126658752d146244ef366f63b8edbb797dc5436
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=openrisc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
or1k-linux-ld: or1k-linux-ld: DWARF error: could not find abbrev number 84
mm/page_alloc.o: in function `watermark_scale_factor_sysctl_handler':
>> page_alloc.c:(.text+0xeaa8): undefined reference to `sysctl_vals'
>> or1k-linux-ld: page_alloc.c:(.text+0xeaac): undefined reference to `sysctl_vals'
`.exit.text' referenced in section `.data' of sound/soc/codecs/tlv320adc3xxx.o: defined in discarded section `.exit.text' of sound/soc/codecs/tlv320adc3xxx.o
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-08-18 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 9:04 [PATCH -next 0/2] watermark related improvement on zone movable Wupeng Ma
2022-08-18 9:04 ` [PATCH -next 1/2] mm: Cap zone movable's min wmark to small value Wupeng Ma
2022-08-18 9:04 ` [PATCH -next 2/2] mm: sysctl: Introduce per zone watermark_scale_factor Wupeng Ma
2022-08-18 11:38 ` kernel test robot
2022-08-18 11:49 ` 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=202208181945.AoDDCp5a-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=corbet@lwn.net \
--cc=jsavitz@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=mcgrof@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yzaikin@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 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.