Re: [PATCH] ravb: fix WARNING in __free_irq()

2015-11-18 Thread David Miller
From: Sergei Shtylyov Date: Thu, 19 Nov 2015 01:39:51 +0300 > When the R8A7795 support was added to the driver, little attention was paid > to the ravb_open() error path: free_irq() for the EMAC interrupt was called > uncoditionally, unlike request_irq(), and in a wrong order as well... > As a

Re: [PATCH] ravb: fix WARNING in __free_irq()

2015-11-18 Thread Simon Horman
On Thu, Nov 19, 2015 at 01:39:51AM +0300, Sergei Shtylyov wrote: > When the R8A7795 support was added to the driver, little attention was paid > to the ravb_open() error path: free_irq() for the EMAC interrupt was called > uncoditionally, unlike request_irq(), and in a wrong order as well... > A

[PATCH] ravb: fix WARNING in __free_irq()

2015-11-18 Thread Sergei Shtylyov
When the R8A7795 support was added to the driver, little attention was paid to the ravb_open() error path: free_irq() for the EMAC interrupt was called uncoditionally, unlike request_irq(), and in a wrong order as well... As a result, on the R-Car gen2 SoCs I started getting the following in cas