Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread 陈华才
> On Wed, 30 Oct 2013, "陈华才" wrote: > >> I use a Loongson-3(MIPS-series CPU) machine, there is a serial port >> integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() >> as the irq handler. Maybe I should move the checking into >> handle_percpu_irq()? > > Why is a device

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread Thomas Gleixner
On Wed, 30 Oct 2013, "陈华才" wrote: > I use a Loongson-3(MIPS-series CPU) machine, there is a serial port > integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() > as the irq handler. Maybe I should move the checking into > handle_percpu_irq()? Why is a device interrupt using

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread 陈华才
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() as the irq handler. Maybe I should move the checking into handle_percpu_irq()? Huacai > On Sat, 28 Sep 2013, Huacai Chen wrote: > >> Some devices (e.g.

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread 陈华才
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() as the irq handler. Maybe I should move the checking into handle_percpu_irq()? Huacai On Sat, 28 Sep 2013, Huacai Chen wrote: Some devices (e.g. serial

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread Thomas Gleixner
On Wed, 30 Oct 2013, 陈华才 wrote: I use a Loongson-3(MIPS-series CPU) machine, there is a serial port integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() as the irq handler. Maybe I should move the checking into handle_percpu_irq()? Why is a device interrupt using

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-30 Thread 陈华才
On Wed, 30 Oct 2013, 陈华才 wrote: I use a Loongson-3(MIPS-series CPU) machine, there is a serial port integrated in the CPU (but it iss buggy), and it use handle_percpu_irq() as the irq handler. Maybe I should move the checking into handle_percpu_irq()? Why is a device interrupt using

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-29 Thread Thomas Gleixner
On Sat, 28 Sep 2013, Huacai Chen wrote: > Some devices (e.g. serial port) setup irq handler at dev open and free > it at dev close. So, sometimes there is no irqaction for a specific > irq. But some buggy devices may send irqs at any time. This patch avoid > the NULL OOPS when irqaction isn't

Re: [PATCH] genirq: Avoid NULL OOPS in irq handling

2013-10-29 Thread Thomas Gleixner
On Sat, 28 Sep 2013, Huacai Chen wrote: Some devices (e.g. serial port) setup irq handler at dev open and free it at dev close. So, sometimes there is no irqaction for a specific irq. But some buggy devices may send irqs at any time. This patch avoid the NULL OOPS when irqaction isn't

[PATCH] genirq: Avoid NULL OOPS in irq handling

2013-09-27 Thread Huacai Chen
Some devices (e.g. serial port) setup irq handler at dev open and free it at dev close. So, sometimes there is no irqaction for a specific irq. But some buggy devices may send irqs at any time. This patch avoid the NULL OOPS when irqaction isn't registered. Signed-off-by: Huacai Chen ---

[PATCH] genirq: Avoid NULL OOPS in irq handling

2013-09-27 Thread Huacai Chen
Some devices (e.g. serial port) setup irq handler at dev open and free it at dev close. So, sometimes there is no irqaction for a specific irq. But some buggy devices may send irqs at any time. This patch avoid the NULL OOPS when irqaction isn't registered. Signed-off-by: Huacai Chen