summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@samba.org>2014-06-12 08:53:08 +0200
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2014-08-05 08:34:28 +0200
commit9be9be2e9a966fe32c1a443c5197f829ecc3028c (patch)
tree874f5a970cb66d959dcb9f09b67696af845722e8 /arch/arm/mach-omap2
parentpowerpc: start loop at section start of start in vmemmap_populated() (diff)
downloadlinux-9be9be2e9a966fe32c1a443c5197f829ecc3028c.tar.xz
linux-9be9be2e9a966fe32c1a443c5197f829ecc3028c.zip
powerpc: Reduce scariness of interrupt frames in stack traces
Some people see things like "Exception: 501" in stack traces in dmesg and assume that means that something has gone badly wrong, when in fact "Exception: 501" just means a device interrupt was taken. This changes "Exception" to "interrupt" to make it clearer that we are just recording the fact of a change in control flow rather than some error condition. Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/arm/mach-omap2')
0 files changed, 0 insertions, 0 deletions