Thread (10 messages) flat view 10 messages, 4 authors, 2015-07-17

Re: [PATCH 3/3] IRQ: Print "unexpected IRQ" messages consistently across architectures

From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2015-07-13 07:14:46
Also in: linux-alpha, linux-arch, linux-mips, linux-s390, linux-sh, lkml

On Mon, Jul 13, 2015 at 12:02 AM, Bjorn Helgaas [off-list ref] wrote:
Many architectures use a variant of "unexpected IRQ trap at vector %x" to
log unexpected IRQs.  This is confusing because (a) it prints the Linux IRQ
number, but "vector" more often refers to a CPU vector number, and (b) it
prints the IRQ number in hex with no base indication, while Linux IRQ
numbers are usually printed in decimal.

Print the same text ("unexpected IRQ %d") across all architectures.

No functional change other than the output text.

Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
---
Thanks!
 arch/m68k/include/asm/hardirq.h    |    2 +-
For m68k:
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

And it looks like m68k can switch to the asm-generic version afterwards...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help