[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201601300835.0L67p1w0%fengguang.wu@intel.com>
Date: Sat, 30 Jan 2016 08:41:20 +0800
From: kbuild test robot <lkp@...el.com>
To: minyard@....org
Cc: kbuild-all@...org, openipmi-developer@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, Jean Delvare <jdelvare@...e.de>,
Andy Lutomirski <luto@...nel.org>,
Corey Minyard <cminyard@...sta.com>
Subject: Re: [PATCH 2/4] dmi: Add a DMI firmware node and handling
Hi Corey,
[auto build test WARNING on char-misc/char-misc-testing]
[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/minyard-acm-org/dmi-Rework-to-get-IPMI-autoloading-from-DMI-tables/20160130-074830
config: i386-randconfig-s0-201604 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text.unlikely+0xe634): Section mismatch in reference from the function dmi_zalloc() to the function .init.text:extend_brk()
The function dmi_zalloc() references
the function __init extend_brk().
This is often because dmi_zalloc lacks a __init
annotation or the annotation of extend_brk is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/octet-stream" (24189 bytes)
Powered by blists - more mailing lists