linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Vinayak Menon <vinmenon@codeaurora.org>
Cc: kbuild-all@01.org, hannes@cmpxchg.org,
	mgorman@techsingularity.net, linux-mm@kvack.org,
	akpm@linux-foundation.org, mhocko@suse.com, vbabka@suse.cz,
	sfr@canb.auug.org.au, pasha.tatashin@oracle.com,
	penguin-kernel@I-love.SAKURA.ne.jp
Subject: Re: [PATCH] mm: fix low-high watermark distance on small systems
Date: Sat, 17 Mar 2018 08:42:17 +0800	[thread overview]
Message-ID: <201803170858.f4QvE89z%fengguang.wu@intel.com> (raw)
In-Reply-To: <1521110079-26870-1-git-send-email-vinmenon@codeaurora.org>

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

Hi Vinayak,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v4.16-rc4]
[also build test ERROR on next-20180316]
[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/Vinayak-Menon/mm-fix-low-high-watermark-distance-on-small-systems/20180317-073051
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   mm/page_alloc.o: In function `__setup_per_zone_wmarks':
>> page_alloc.c:(.text+0xa10): undefined reference to `__udivdi3'
>> page_alloc.c:(.text+0xa41): undefined reference to `__umoddi3'
   page_alloc.c:(.text+0xa58): undefined reference to `__udivdi3'

---
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: 6733 bytes --]

  parent reply	other threads:[~2018-03-17  0:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 10:34 Vinayak Menon
2018-03-15 14:34 ` Minchan Kim
2018-03-16 11:03   ` Vinayak Menon
2018-03-20 10:16     ` Minchan Kim
2018-03-20 10:52       ` Vinayak Menon
2018-03-20 11:29         ` Minchan Kim
2018-03-22 13:43           ` Vinayak Menon
2018-03-17  0:42 ` kbuild test robot [this message]
2018-03-17  1:40 ` 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=201803170858.f4QvE89z%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=sfr@canb.auug.org.au \
    --cc=vbabka@suse.cz \
    --cc=vinmenon@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox