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

On Mon, Jul 13, 2015 at 12:02 AM, Bjorn Helgaas 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

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

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 numbe