summaryrefslogtreecommitdiffstats
path: root/drivers/ide/ide-gd.h
diff options
context:
space:
mode:
authorMark Nelson <markn@au1.ibm.com>2010-05-26 22:56:04 +0200
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-07-09 03:28:32 +0200
commit68581e9350506dcf0160c3a29dcd21e5a848cda7 (patch)
tree5e8a5b7acc16f09541bd25679c3822fb5788b0a3 /drivers/ide/ide-gd.h
parentpowerpc/pseries: Rename RAS_VECTOR_OFFSET to RTAS_VECTOR_EXTERNAL_INTERRUPT a... (diff)
downloadlinux-68581e9350506dcf0160c3a29dcd21e5a848cda7.tar.xz
linux-68581e9350506dcf0160c3a29dcd21e5a848cda7.zip
powerpc/pseries: Add WARN_ON() to request_event_sources_irqs() on irq allocation/request failure
At the moment if request_event_sources_irqs() can't allocate or request the interrupt, it just does a KERN_ERR printk. This may be fine for the existing RAS code where if we miss an EPOW event it just means that the event won't be logged and if we miss one of the RAS errors then we could miss an event that we perhaps should take action on. But, for the upcoming IO events code that will use event-sources if we can't allocate or request the interrupt it means we'd potentially miss an interrupt from the device. So, let's add a WARN_ON() in this error case so that we're a bit more vocal when something's amiss. While we're at it, also use pr_err() to neaten the code up a bit. Signed-off-by: Mark Nelson <markn@au1.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'drivers/ide/ide-gd.h')
0 files changed, 0 insertions, 0 deletions