linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 123/232] WARNING: mm/built-in.o(.text+0x2b91d): Section mismatch in reference from the function move_pfn_range_to_zone() to the function .meminit.text:init_currently_empty_zone()
Date: Fri, 31 Mar 2017 10:12:03 +0800	[thread overview]
Message-ID: <201703311001.YZg1DJvI%fengguang.wu@intel.com> (raw)

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   c9e652f1af277422827824aa002e12f35c9f0627
commit: 9692e1fa46418e3faab906e40e03b33024016292 [123/232] mm, memory_hotplug: do not associate hotadded memory to zones until online
config: i386-randconfig-r0-201713 (attached as .config)
compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
reproduce:
        git checkout 9692e1fa46418e3faab906e40e03b33024016292
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

>> WARNING: mm/built-in.o(.text+0x2b91d): Section mismatch in reference from the function move_pfn_range_to_zone() to the function .meminit.text:init_currently_empty_zone()
   The function move_pfn_range_to_zone() references
   the function __meminit init_currently_empty_zone().
   This is often because move_pfn_range_to_zone lacks a __meminit
   annotation or the annotation of init_currently_empty_zone is wrong.
--
>> WARNING: mm/built-in.o(.text+0x2b9c5): Section mismatch in reference from the function move_pfn_range_to_zone() to the function .meminit.text:memmap_init_zone()
   The function move_pfn_range_to_zone() references
   the function __meminit memmap_init_zone().
   This is often because move_pfn_range_to_zone lacks a __meminit
   annotation or the annotation of memmap_init_zone is wrong.

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

                 reply	other threads:[~2017-03-31  2:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201703311001.YZg1DJvI%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.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