From: kbuild test robot <lkp@intel.com>
To: Geliang Tang <geliangtang@163.com>
Cc: kbuild-all@01.org, Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Russell King <linux@arm.linux.org.uk>,
Geliang Tang <geliangtang@163.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: davinci: fix a problematic usage of WARN()
Date: Thu, 26 Nov 2015 04:21:09 +0800 [thread overview]
Message-ID: <201511260435.1AHQOCP1%fengguang.wu@intel.com> (raw)
In-Reply-To: <50fd45fb78403b66381569a8c9ada6b17433e2d9.1448460525.git.geliangtang@163.com>
[-- Attachment #1: Type: text/plain, Size: 3708 bytes --]
Hi Geliang,
[auto build test ERROR on arm-soc/for-next]
[also build test ERROR on v4.4-rc2 next-20151124]
url: https://github.com/0day-ci/linux/commits/Geliang-Tang/ARM-davinci-fix-a-problematic-usage-of-WARN/20151125-221653
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git for-next
config: arm-davinci_all_defconfig (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=arm
All error/warnings (new ones prefixed by >>):
In file included from arch/arm/include/asm/bug.h:62:0,
from arch/arm/include/asm/div64.h:63,
from include/linux/kernel.h:136,
from arch/arm/mach-davinci/board-dm355-evm.c:11:
arch/arm/mach-davinci/board-dm355-evm.c: In function 'dm355_evm_init':
>> include/asm-generic/bug.h:74:72: error: expected expression before ')' token
#define __WARN_printf(arg...) warn_slowpath_fmt(__FILE__, __LINE__, arg)
^
include/asm-generic/bug.h:97:3: note: in expansion of macro '__WARN_printf'
__WARN_printf(format); \
^
>> arch/arm/mach-davinci/board-dm355-evm.c:387:7: note: in expansion of macro 'WARN'
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
arch/arm/mach-davinci/board-dm355-evm.c:387:6: warning: value computed is not used [-Wunused-value]
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
>> arch/arm/mach-davinci/board-dm355-evm.c:387:58: error: expected statement before ')' token
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
--
In file included from arch/arm/include/asm/bug.h:62:0,
from arch/arm/include/asm/div64.h:63,
from include/linux/kernel.h:136,
from arch/arm/mach-davinci/board-dm355-leopard.c:10:
arch/arm/mach-davinci/board-dm355-leopard.c: In function 'dm355_leopard_init':
>> include/asm-generic/bug.h:74:72: error: expected expression before ')' token
#define __WARN_printf(arg...) warn_slowpath_fmt(__FILE__, __LINE__, arg)
^
include/asm-generic/bug.h:97:3: note: in expansion of macro '__WARN_printf'
__WARN_printf(format); \
^
>> arch/arm/mach-davinci/board-dm355-leopard.c:245:7: note: in expansion of macro 'WARN'
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
arch/arm/mach-davinci/board-dm355-leopard.c:245:6: warning: value computed is not used [-Wunused-value]
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
>> arch/arm/mach-davinci/board-dm355-leopard.c:245:58: error: expected statement before ')' token
if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
^
vim +387 arch/arm/mach-davinci/board-dm355-evm.c
381
382 gpio_request(1, "dm9000");
383 gpio_direction_input(1);
384 dm355evm_dm9000_rsrc[2].start = gpio_to_irq(1);
385
386 aemif = clk_get(&dm355evm_dm9000.dev, "aemif");
> 387 if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
388 clk_prepare_enable(aemif);
389
390 platform_add_devices(davinci_evm_devices,
---
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: 18871 bytes --]
next prev parent reply other threads:[~2015-11-25 20:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 13:12 [PATCH 1/7] drm/msm/mdp: fix a problematic usage of WARN_ON() Geliang Tang
2015-11-25 13:12 ` [PATCH 2/7] drm/vmwgfx: " Geliang Tang
2015-11-25 13:12 ` [PATCH 3/7] iio: " Geliang Tang
2015-11-25 13:12 ` [PATCH 4/7] iwlwifi: fix a problematic usage of WARN_ON_ONCE() Geliang Tang
2015-11-25 13:12 ` [PATCH 5/7] vfio: fix a problematic usage of WARN() Geliang Tang
2015-11-25 13:12 ` [PATCH 6/7] ARM: davinci: " Geliang Tang
2015-11-25 13:12 ` [PATCH 7/7] powerpc: " Geliang Tang
2015-11-26 5:25 ` Michael Ellerman
2015-11-25 13:39 ` [PATCH 6/7] ARM: davinci: " Arnd Bergmann
2015-11-25 14:13 ` [PATCH v2] " Geliang Tang
2015-11-25 20:21 ` kbuild test robot [this message]
2015-11-25 20:28 ` Arnd Bergmann
2015-11-26 0:35 ` [PATCH v3] " Geliang Tang
2015-12-15 9:58 ` Sekhar Nori
2015-11-25 13:35 ` [PATCH 5/7] vfio: " Alex Williamson
2015-11-25 13:47 ` [PATCH 4/7] iwlwifi: fix a problematic usage of WARN_ON_ONCE() Grumbach, Emmanuel
2015-11-25 13:14 ` [PATCH 3/7] iio: fix a problematic usage of WARN_ON() Lars-Peter Clausen
2015-11-25 15:50 ` [PATCH 2/7] drm/vmwgfx: " Sinclair Yeh
2015-11-26 14:51 ` Thomas Hellstrom
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=201511260435.1AHQOCP1%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=geliangtang@163.com \
--cc=kbuild-all@01.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.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
all inboxes | Powered by JetHome®