From: kbuild test robot <lkp@intel.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Russell King <linux@arm.linux.org.uk>,
Marc Zyngier <marc.zyngier@arm.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Stephen Boyd <sboyd@codeaurora.org>,
John Stultz <john.stultz@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, patches@linaro.org,
linaro-kernel@lists.linaro.org,
Sumit Semwal <sumit.semwal@linaro.org>,
Dirk Behme <dirk.behme@de.bosch.com>,
Daniel Drake <drake@endlessm.com>,
Dmitry Pervushin <dpervushin@gmail.com>,
Tim Sander <tim@krieglstein.org>, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ
Date: Mon, 21 Dec 2015 06:12:05 +0800 [thread overview]
Message-ID: <201512210618.hMZqsBKl%fengguang.wu@intel.com> (raw)
In-Reply-To: <1450644757-18734-5-git-send-email-daniel.thompson@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
Hi Daniel,
[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151218]
[cannot apply to tip/irq/core]
url: https://github.com/0day-ci/linux/commits/Daniel-Thompson/irq-arm-Use-FIQ-for-NMI-backtrace-when-possible/20151221-045854
config: arm-iop-adma (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 errors (new ones prefixed by >>):
arch/arm/kernel/traps.c: In function 'handle_fiq_as_nmi':
>> arch/arm/kernel/traps.c:489:2: error: implicit declaration of function 'handle_arch_irq' [-Werror=implicit-function-declaration]
handle_arch_irq(regs);
^
cc1: some warnings being treated as errors
vim +/handle_arch_irq +489 arch/arm/kernel/traps.c
483 * Either the interrupt controller supports FIQ, meaning it will
484 * do the right thing with this call, or we will end up treating a
485 * spurious FIQ (which is normally fatal) as though it were an IRQ
486 * which, although it risks deadlock, still gives us a sporting
487 * chance of surviving long enough to log errors.
488 */
> 489 handle_arch_irq(regs);
490
491 nmi_exit();
492
---
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: 20864 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: lkp@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ
Date: Mon, 21 Dec 2015 06:12:05 +0800 [thread overview]
Message-ID: <201512210618.hMZqsBKl%fengguang.wu@intel.com> (raw)
In-Reply-To: <1450644757-18734-5-git-send-email-daniel.thompson@linaro.org>
Hi Daniel,
[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151218]
[cannot apply to tip/irq/core]
url: https://github.com/0day-ci/linux/commits/Daniel-Thompson/irq-arm-Use-FIQ-for-NMI-backtrace-when-possible/20151221-045854
config: arm-iop-adma (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 errors (new ones prefixed by >>):
arch/arm/kernel/traps.c: In function 'handle_fiq_as_nmi':
>> arch/arm/kernel/traps.c:489:2: error: implicit declaration of function 'handle_arch_irq' [-Werror=implicit-function-declaration]
handle_arch_irq(regs);
^
cc1: some warnings being treated as errors
vim +/handle_arch_irq +489 arch/arm/kernel/traps.c
483 * Either the interrupt controller supports FIQ, meaning it will
484 * do the right thing with this call, or we will end up treating a
485 * spurious FIQ (which is normally fatal) as though it were an IRQ
486 * which, although it risks deadlock, still gives us a sporting
487 * chance of surviving long enough to log errors.
488 */
> 489 handle_arch_irq(regs);
490
491 nmi_exit();
492
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 20864 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151221/90a009bc/attachment-0001.obj>
next prev parent reply other threads:[~2015-12-20 22:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 20:52 [PATCH 4.4-rc5 v22 0/4] irq/arm: Use FIQ for NMI backtrace (when possible) Daniel Thompson
2015-12-20 20:52 ` Daniel Thompson
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 1/4] irqchip: gic: Optimize locking in gic_raise_softirq Daniel Thompson
2015-12-20 20:52 ` Daniel Thompson
2016-01-07 14:31 ` Marc Zyngier
2016-01-07 14:31 ` Marc Zyngier
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 2/4] irqchip: gic: Make gic_raise_softirq FIQ-safe Daniel Thompson
2015-12-20 20:52 ` Daniel Thompson
2016-01-07 14:35 ` Marc Zyngier
2016-01-07 14:35 ` Marc Zyngier
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 3/4] irqchip: gic: Introduce plumbing for IPI FIQ Daniel Thompson
2015-12-20 20:52 ` Daniel Thompson
2016-01-07 17:06 ` Marc Zyngier
2016-01-07 17:06 ` Marc Zyngier
2016-01-11 12:02 ` Daniel Thompson
2016-01-11 12:02 ` Daniel Thompson
2015-12-20 20:52 ` [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ Daniel Thompson
2015-12-20 20:52 ` Daniel Thompson
2015-12-20 22:12 ` kbuild test robot [this message]
2015-12-20 22:12 ` kbuild test robot
2016-01-04 10:00 ` Daniel Thompson
2016-01-04 10:00 ` Daniel Thompson
2015-12-20 22:52 ` kbuild test robot
2015-12-20 22:52 ` kbuild test robot
2016-01-04 10:05 ` Daniel Thompson
2016-01-04 10:05 ` Daniel Thompson
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=201512210618.hMZqsBKl%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dirk.behme@de.bosch.com \
--cc=dpervushin@gmail.com \
--cc=drake@endlessm.com \
--cc=jason@lakedaemon.net \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@01.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=patches@linaro.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sboyd@codeaurora.org \
--cc=sumit.semwal@linaro.org \
--cc=tglx@linutronix.de \
--cc=tim@krieglstein.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.