From: kbuild test robot <lkp@intel.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86/e820: Use much less memory for e820/e820_saved, save up to 120k
Date: Fri, 9 Sep 2016 05:42:38 +0800 [thread overview]
Message-ID: <201609090519.o65LD4yF%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160908195033.1799-2-dvlasenk@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
Hi Denys,
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on v4.8-rc5 next-20160908]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Denys-Vlasenko/x86-e820-mark-some-static-functions-__init/20160909-035802
config: x86_64-randconfig-i0-201636 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.data+0x1b398): Section mismatch in reference from the variable e820_saved to the variable .init.data:initial_e820_saved
The variable e820_saved references
the variable __initdata initial_e820_saved
If the reference is valid then annotate the
variable with or __refdata (see linux/init.h) or name the variable:
--
>> WARNING: vmlinux.o(.data+0x1b3a0): Section mismatch in reference from the variable e820 to the variable .init.data:initial_e820
The variable e820 references
the variable __initdata initial_e820
If the reference is valid then annotate the
variable with or __refdata (see linux/init.h) or name the variable:
---
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: 14913 bytes --]
prev parent reply other threads:[~2016-09-08 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 19:50 [PATCH 1/2] x86/e820: mark some static functions __init Denys Vlasenko
2016-09-08 19:50 ` [PATCH 2/2] x86/e820: Use much less memory for e820/e820_saved, save up to 120k Denys Vlasenko
2016-09-08 21:42 ` 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=201609090519.o65LD4yF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®