diff options
| author | Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> | 2014-11-22 16:48:15 +0300 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2014-11-27 19:15:33 +0300 |
| commit | 44cb09c23f8e5838f24ef47d43dd2804b71b3a65 (patch) | |
| tree | 250e9d1789881a744d5bf88ee7e6322be3ffdf11 /arch/arm/mm/mmu.c | |
| parent | 119acbd24c54d73c8941f43f16817c3417237413 (diff) | |
| download | linux-44cb09c23f8e5838f24ef47d43dd2804b71b3a65.tar.xz | |
ARM: 8218/1: warn if bad IRQ was scheduled
If somebody causes an unexpected bad IRQ, this even will be unnoticed in
both dmesg and system logs. If the "bad" IRQ is stuck, the device will
just hang silently w/o reporting anything. Compare this to the generic
behaviour (from include/asm-generic/hardirq.h) which prints a message
with critical level. So to help everybody, include the same message into
ARM-specific ack_bad_irq().
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/mm/mmu.c')
0 files changed, 0 insertions, 0 deletions