From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
matthew.garrett@nebula.com, rui.zhang@intel.com,
Chen Yu <yu.c.chen@intel.com>
Subject: Re: [PATCH] ACPI: Do not report _OSI("Darwin") when acpi_osi=!Darwin provided
Date: Mon, 1 Feb 2016 06:45:19 +0800 [thread overview]
Message-ID: <201602010635.ezE8Ul92%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454251904-7514-1-git-send-email-yu.c.chen@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Hi Chen,
[auto build test WARNING on pm/linux-next]
[also build test WARNING on v4.5-rc1 next-20160129]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Chen-Yu/ACPI-Do-not-report-_OSI-Darwin-when-acpi_osi-Darwin-provided/20160131-224855
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: arm64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
>> WARNING: drivers/built-in.o(.text+0x2b8f38): Section mismatch in reference from the function acpi_osi_handler() to the variable .init.data:$d
The function acpi_osi_handler() references
the variable __initdata $d.
This is often because acpi_osi_handler lacks a __initdata
annotation or the annotation of $d 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: 48147 bytes --]
prev parent reply other threads:[~2016-01-31 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 14:51 [PATCH] ACPI: Do not report _OSI("Darwin") when acpi_osi=!Darwin provided Chen Yu
2016-01-31 15:53 ` kbuild test robot
2016-01-31 22:45 ` 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=201602010635.ezE8Ul92%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).