The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled)
running IRQ handlers with interrupts enabled can cause stack overflows
when the interrupt line of the issuing device is still active.
This patch removes
On Fri, Feb 27, 2015 at 04:48:39PM +0100, Valentin Rothberg wrote:
On Fri, Feb 27, 2015 at 4:24 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
commit e58aa3d2d0cc
On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled)
running IRQ handlers with interrupts enabled can cause stack overflows
when the
On Fri, Feb 27, 2015 at 4:24 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled)
running IRQ