Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1300596 > unrolled thread
| Started by | Daniel Thompson <daniel.thompson@linaro.org> |
|---|---|
| First post | 2016-01-04 11:10 +0100 |
| Last post | 2016-01-04 11:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ Daniel Thompson <daniel.thompson@linaro.org> - 2016-01-04 11:10 +0100
| From | Daniel Thompson <daniel.thompson@linaro.org> |
|---|---|
| Date | 2016-01-04 11:10 +0100 |
| Subject | Re: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ |
| Message-ID | <qNafo-23H-9@gated-at.bofh.it> |
On 20/12/15 22:12, kbuild test robot wrote: > 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 Thanks. I'll look at this. > 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web