linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: WARNING: modpost: vmlinux.o(.text.unlikely+0xe24): Section mismatch in reference from the function .remove_pud_table() to the function .meminit.text:.split_kernel_mapping()
Date: Fri, 17 Jul 2020 07:08:20 +0800	[thread overview]
Message-ID: <202007170716.SgwTy0ZB%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   07a56bb875afbe39dabbf6ba7b83783d166863db
commit: ec4abf1e70cf6a3fe6e571d640260005c997c6e1 powerpc/mm/hash64: use _PAGE_PTE when checking for pte_present
date:   2 months ago
config: powerpc-randconfig-c022-20200716 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0

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 >>):

>> WARNING: modpost: vmlinux.o(.text.unlikely+0xe24): Section mismatch in reference from the function .remove_pud_table() to the function .meminit.text:.split_kernel_mapping()
   The function .remove_pud_table() references
   the function __meminit .split_kernel_mapping().
   This is often because .remove_pud_table lacks a __meminit
   annotation or the annotation of .split_kernel_mapping 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: 31660 bytes --]

                 reply	other threads:[~2020-07-16 23:20 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=202007170716.SgwTy0ZB%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    /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).