Re: dummy irq trace 'Flags mismatch'

2013-04-30 Thread Jonathan Corbet
On Tue, 30 Apr 2013 06:59:22 +0200 (CEST) Jiri Kosina wrote: > Or have it depend on CONFIG_EXPERT would probably make most sense ... ? We could also just have it tell you when you screwed up? Something like the following (compile tested only)? jon --- dummy-irq: require the user to specify an

Re: dummy irq trace 'Flags mismatch'

2013-04-29 Thread Jiri Kosina
On Mon, 29 Apr 2013, Dave Jones wrote: > When set to built-in, the dummy irq driver causes this trace when I boot.. > > [3.996055] genirq: Flags mismatch irq 0. 0080 (dummy_irq) vs. > 00015a20 (timer) > [3.997055] Pid: 1, comm: swapper/0 Not tainted 3.9.0+ #29 > [3.997768] Call T

dummy irq trace 'Flags mismatch'

2013-04-29 Thread Dave Jones
When set to built-in, the dummy irq driver causes this trace when I boot.. [3.996055] genirq: Flags mismatch irq 0. 0080 (dummy_irq) vs. 00015a20 (timer) [3.997055] Pid: 1, comm: swapper/0 Not tainted 3.9.0+ #29 [3.997768] Call Trace: [3.998127] [] __setup_irq+0x515/0x550 [