Re: [PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

On Fri, Mar 30, 2018 at 02:51:55PM +0900, Ji-Hun Kim wrote: > There was no code for handling memory leaks of device_init_rings() and > request_irq(). It needs to free allocated memory in the device_init_rings() > , when request_irq() is failed. Add freeing sequences of irq and device > init rings.

Re: [PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

On Fri, Mar 30, 2018 at 02:51:55PM +0900, Ji-Hun Kim wrote: > There was no code for handling memory leaks of device_init_rings() and > request_irq(). It needs to free allocated memory in the device_init_rings() > , when request_irq() is failed. Add freeing sequences of irq and device > init rings.

[PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

There was no code for handling memory leaks of device_init_rings() and request_irq(). It needs to free allocated memory in the device_init_rings() , when request_irq() is failed. Add freeing sequences of irq and device init rings. Signed-off-by: Ji-Hun Kim --- It's

[PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

There was no code for handling memory leaks of device_init_rings() and request_irq(). It needs to free allocated memory in the device_init_rings() , when request_irq() is failed. Add freeing sequences of irq and device init rings. Signed-off-by: Ji-Hun Kim --- It's additional memory leak