From: kbuild test robot <lkp@intel.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: kbuild-all@01.org, nsekhar@ti.com, khilman@kernel.org,
linux@armlinux.org.uk, kaloz@openwrt.org, khalasa@piap.pl,
aaro.koskinen@iki.fi, tony@atomide.com, jason@lakedaemon.net,
andrew@lunn.ch, sebastian.hesselbarth@gmail.com,
gregory.clement@free-electrons.com, daniel@zonque.org,
haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
marek.vasut@gmail.com, slapin@ossfans.org, jic23@cam.ac.uk,
kgene@kernel.org, krzk@kernel.org, ralf@linux-mips.org,
ysato@users.sourceforge.jp, dalias@libc.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 04/11] x86: geode: constify gpio_led
Date: Sat, 23 Dec 2017 15:50:08 +0800 [thread overview]
Message-ID: <201712231558.6NpYlcSM%fengguang.wu@intel.com> (raw)
In-Reply-To: <807e8a857faf9e01a2e776fda95e883bf1f842f9.1513756005.git.arvind.yadav.cs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Hi Arvind,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on arm-soc/for-next]
[also build test WARNING on v4.15-rc4 next-20171222]
[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/Arvind-Yadav/constify-gpio_led/20171223-142117
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git for-next
config: i386-randconfig-s1-201751 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.data+0x16554): Section mismatch in reference from the variable geos_leds_data to the variable .init.rodata:geos_leds
The variable geos_leds_data references
the variable __initconst geos_leds
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/gzip, Size: 31296 bytes --]
next prev parent reply other threads:[~2017-12-23 7:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 8:47 [PATCH 00/11] " Arvind Yadav
2017-12-20 8:47 ` [PATCH 01/11] MIPS: Alchemy: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 02/11] MIPS: AR7: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 03/11] MIPS: TXX9: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 04/11] x86: geode: " Arvind Yadav
2017-12-23 7:50 ` kbuild test robot [this message]
2017-12-20 8:47 ` [PATCH 05/11] sh: mach-rsk: rsk7203: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 06/11] ARM: davinci: " Arvind Yadav
2017-12-23 10:01 ` Sekhar Nori
2017-12-20 8:47 ` [PATCH 07/11] ARM: ixp4xx: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 08/11] ARM: OMAP1: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 09/11] ARM: orion5x: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 10/11] ARM: s3c24xx: " Arvind Yadav
2017-12-20 8:47 ` [PATCH 11/11] ARM: pxa: " Arvind Yadav
2017-12-24 17:54 ` kbuild test robot
2017-12-25 13:04 ` arvindY
2017-12-23 10:13 ` [PATCH 00/11] " Russell King - ARM Linux
2017-12-25 13:07 ` arvindY
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=201712231558.6NpYlcSM%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=andrew@lunn.ch \
--cc=arvind.yadav.cs@gmail.com \
--cc=dalias@libc.org \
--cc=daniel@zonque.org \
--cc=gregory.clement@free-electrons.com \
--cc=haojian.zhuang@gmail.com \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jic23@cam.ac.uk \
--cc=kaloz@openwrt.org \
--cc=kbuild-all@01.org \
--cc=kgene@kernel.org \
--cc=khalasa@piap.pl \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=mingo@redhat.com \
--cc=nsekhar@ti.com \
--cc=ralf@linux-mips.org \
--cc=robert.jarzmik@free.fr \
--cc=sebastian.hesselbarth@gmail.com \
--cc=slapin@ossfans.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=ysato@users.sourceforge.jp \
/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®