linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Ashish Mhetre <amhetre@nvidia.com>
Cc: kbuild-all@01.org, vdumpa@nvidia.com, mcgrof@kernel.org,
	keescook@chromium.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	Snikam@nvidia.com, Ashish Mhetre <amhetre@nvidia.com>
Subject: Re: [PATCH] mm: Expose lazy vfree pages to control via sysctl
Date: Sat, 5 Jan 2019 02:29:28 +0800	[thread overview]
Message-ID: <201901050245.eqckFBTE%fengguang.wu@intel.com> (raw)
In-Reply-To: <1546616141-486-1-git-send-email-amhetre@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

Hi Hiroshi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.20 next-20190103]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Ashish-Mhetre/mm-Expose-lazy-vfree-pages-to-control-via-sysctl/20190105-003852
config: sh-rsk7269_defconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.2.0 make.cross ARCH=sh 

All errors (new ones prefixed by >>):

>> kernel/sysctl.o:(.data+0x2d4): undefined reference to `sysctl_lazy_vfree_pages'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 10820 bytes --]

  parent reply	other threads:[~2019-01-04 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 15:35 [PATCH] mm: Expose lazy vfree pages to control via sysctl Ashish Mhetre
2019-01-04 18:03 ` Matthew Wilcox
2019-01-06  8:42   ` Ashish Mhetre
2019-01-21  8:06     ` Ashish Mhetre
2019-01-04 18:29 ` kbuild test robot [this message]
2019-01-04 18:30 ` kbuild 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=201901050245.eqckFBTE%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Snikam@nvidia.com \
    --cc=amhetre@nvidia.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=vdumpa@nvidia.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).