All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 14484/14891] WARNING: modpost: vmlinux.o(.text.unlikely+0x2830): Section mismatch in reference from the function pmax_setup_memory_region() to the function .meminit.text:memblock_add()
Date: Tue, 13 Oct 2020 21:07:31 +0800	[thread overview]
Message-ID: <202010132128.ldjunbjr-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f2fb1afc57304f9dd68c20a08270e287470af2eb
commit: e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c [14484/14891] MIPS: replace add_memory_region with memblock
config: mips-decstation_r4k_defconfig (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips 

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

All warnings (new ones prefixed by >>, old ones prefixed by <<):

<< WARNING: modpost: vmlinux.o(.text.unlikely+0x2834): Section mismatch in reference from the function pmax_setup_memory_region() to the function .init.text:add_memory_region()
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x2830): Section mismatch in reference from the function pmax_setup_memory_region() to the function .meminit.text:memblock_add()
The function pmax_setup_memory_region() references
the function __meminit memblock_add().
This is often because pmax_setup_memory_region lacks a __meminit
annotation or the annotation of memblock_add is wrong.

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 14484/14891] WARNING: modpost: vmlinux.o(.text.unlikely+0x2830): Section mismatch in reference from the function pmax_setup_memory_region() to the function .meminit.text:memblock_add()
Date: Tue, 13 Oct 2020 21:07:31 +0800	[thread overview]
Message-ID: <202010132128.ldjunbjr-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f2fb1afc57304f9dd68c20a08270e287470af2eb
commit: e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c [14484/14891] MIPS: replace add_memory_region with memblock
config: mips-decstation_r4k_defconfig (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips 

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

All warnings (new ones prefixed by >>, old ones prefixed by <<):

<< WARNING: modpost: vmlinux.o(.text.unlikely+0x2834): Section mismatch in reference from the function pmax_setup_memory_region() to the function .init.text:add_memory_region()
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x2830): Section mismatch in reference from the function pmax_setup_memory_region() to the function .meminit.text:memblock_add()
The function pmax_setup_memory_region() references
the function __meminit memblock_add().
This is often because pmax_setup_memory_region lacks a __meminit
annotation or the annotation of memblock_add is wrong.

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

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

             reply	other threads:[~2020-10-13 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 13:07 kernel test robot [this message]
2020-10-13 13:07 ` [linux-next:master 14484/14891] WARNING: modpost: vmlinux.o(.text.unlikely+0x2830): Section mismatch in reference from the function pmax_setup_memory_region() to the function .meminit.text:memblock_add() kernel 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=202010132128.ldjunbjr-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.