From: kbuild test robot <lkp@intel.com>
To: Dennis Chen <dennis.chen@arm.com>
Cc: kbuild-all@01.org, linux-arm-kernel@lists.infradead.org,
nd@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
Steve Capper <steve.capper@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
linux-mm@kvack.org, linux-acpi@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: memblock Add some new functions to address the mem limit issue
Date: Thu, 23 Jun 2016 23:26:36 +0800 [thread overview]
Message-ID: <201606232319.4gbhuXin%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466681415-8058-1-git-send-email-dennis.chen@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Hi,
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on v4.7-rc4 next-20160623]
[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/Dennis-Chen/mm-memblock-Add-some-new-functions-to-address-the-mem-limit-issue/20160623-193344
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux for-next/core
config: x86_64-randconfig-s0-06232144 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text.unlikely+0x330c): Section mismatch in reference from the function __find_max_addr() to the variable .meminit.data:memblock
The function __find_max_addr() references
the variable __meminitdata memblock.
This is often because __find_max_addr lacks a __meminitdata
annotation or the annotation of memblock 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/octet-stream, Size: 21054 bytes --]
prev parent reply other threads:[~2016-06-23 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 11:30 Dennis Chen
2016-06-23 11:30 ` [PATCH 2/2] arm64:acpi Fix the acpi alignment exeception when 'mem=' specified Dennis Chen
2016-06-23 12:42 ` Mark Rutland
2016-06-24 2:31 ` Dennis Chen
2016-06-23 12:57 ` [PATCH 1/2] mm: memblock Add some new functions to address the mem limit issue Mark Rutland
2016-06-24 2:28 ` Dennis Chen
2016-06-23 15:26 ` kbuild test robot [this message]
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=201606232319.4gbhuXin%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dennis.chen@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=nd@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.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