All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 1/3] meminfo_extra: introduce meminfo extra
Date: Mon, 23 Mar 2020 19:02:24 +0800	[thread overview]
Message-ID: <202003231848.63tbfVkf%lkp@intel.com> (raw)
In-Reply-To: <20200323080503.6224-2-jaewon31.kim@samsung.com>

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

Hi Jaewon,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on linux/master linus/master v5.6-rc7 next-20200323]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Jaewon-Kim/meminfo_extra-introduce-meminfo-extra/20200323-174445
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 6203da9803017701da5782998157d9826215059d
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: mm/page_alloc.o: in function `show_free_areas':
>> page_alloc.c:(.text+0x2555): undefined reference to `show_meminfo_extra'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

  parent reply	other threads:[~2020-03-23 11:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200323080507epcas1p44cdb9ecb70a7a7395b3acddeda3cfd89@epcas1p4.samsung.com>
2020-03-23  8:05 ` [RFC PATCH v2 0/3] meminfo_extra: introduce meminfo extra Jaewon Kim
2020-03-23  8:05   ` [RFC PATCH v2 1/3] " Jaewon Kim
2020-03-23  9:53     ` Greg KH
2020-03-24  9:11       ` Jaewon Kim
2020-03-24 10:11         ` Greg KH
2020-03-24 11:37           ` Jaewon Kim
2020-03-24 11:46             ` Greg KH
2020-03-24 12:53               ` Jaewon Kim
2020-03-24 13:19                 ` Greg KH
2020-03-26  8:21                   ` Jaewon Kim
2020-03-29  7:19                 ` Leon Romanovsky
2020-03-29  7:23                   ` Greg KH
2020-03-29  8:19                     ` Leon Romanovsky
2020-03-25 18:23               ` Alexey Dobriyan
2020-03-23 11:02     ` kbuild test robot [this message]
2020-03-23 12:00     ` Dave Young
2020-03-23 12:36     ` kbuild test robot
2020-03-23  8:05   ` [RFC PATCH v2 2/3] mm: zsmalloc: include zs page size in " Jaewon Kim
2020-03-23  8:05   ` [RFC PATCH v2 3/3] android: ion: include system heap " Jaewon Kim
2020-03-23  9:49     ` Greg KH
2020-03-25 18:12   ` [RFC PATCH v2 0/3] meminfo_extra: introduce " Alexey Dobriyan

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=202003231848.63tbfVkf%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.