From: kbuild test robot <lkp@intel.com>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: kbuild-all@01.org, Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asm-generic/io.h: remove unnecessary include of linux/vmalloc.h
Date: Fri, 8 Sep 2017 03:36:45 +0800 [thread overview]
Message-ID: <201709080336.iO3VHdeU%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170905112727.13668-1-tklauser@distanz.ch>
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
Hi Tobias,
[auto build test ERROR on v4.13]
[also build test ERROR on next-20170907]
[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/Tobias-Klauser/asm-generic-io-h-remove-unnecessary-include-of-linux-vmalloc-h/20170908-012111
config: arm-shmobile_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
>> arch/arm/mach-shmobile/pm-r8a7779.c:24:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'r8a7779_sysc_init'
static void __init r8a7779_sysc_init(void)
^~~~~~~~~~~~~~~~~
>> arch/arm/mach-shmobile/pm-r8a7779.c:35:13: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'r8a7779_pm_init'
void __init r8a7779_pm_init(void)
^~~~~~~~~~~~~~~
vim +24 arch/arm/mach-shmobile/pm-r8a7779.c
f40aaf6da Magnus Damm 2012-01-10 23
a662c0826 Magnus Damm 2012-01-10 @24 static void __init r8a7779_sysc_init(void)
a662c0826 Magnus Damm 2012-01-10 25 {
053239987 Geert Uytterhoeven 2016-06-28 26 rcar_sysc_init(0xffd85000, 0x0131000e);
a662c0826 Magnus Damm 2012-01-10 27 }
a662c0826 Magnus Damm 2012-01-10 28
f40aaf6da Magnus Damm 2012-01-10 29 #else /* CONFIG_PM || CONFIG_SMP */
f40aaf6da Magnus Damm 2012-01-10 30
f40aaf6da Magnus Damm 2012-01-10 31 static inline void r8a7779_sysc_init(void) {}
f40aaf6da Magnus Damm 2012-01-10 32
f40aaf6da Magnus Damm 2012-01-10 33 #endif /* CONFIG_PM || CONFIG_SMP */
f40aaf6da Magnus Damm 2012-01-10 34
a662c0826 Magnus Damm 2012-01-10 @35 void __init r8a7779_pm_init(void)
:::::: The code at line 24 was first introduced by commit
:::::: a662c08260fac126059a148cbd1061e71e806b4a ARM: mach-shmobile: r8a7779 power domain support V2
:::::: TO: Magnus Damm <damm@opensource.se>
:::::: CC: Paul Mundt <lethal@linux-sh.org>
---
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: 27647 bytes --]
next prev parent reply other threads:[~2017-09-07 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 11:27 [PATCH] asm-generic/io.h: remove unnecessary include of linux/vmalloc.h Tobias Klauser
2017-09-05 15:11 ` Arnd Bergmann
2017-09-05 15:21 ` Tobias Klauser
2017-09-05 20:49 ` Arnd Bergmann
2017-11-07 10:24 ` Tobias Klauser
2017-09-07 19:31 ` kbuild test robot
2017-09-07 19:36 ` kbuild test robot [this message]
2017-09-08 8:22 ` Tobias Klauser
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=201709080336.iO3VHdeU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tklauser@distanz.ch \
/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).