Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

* Qi Hou [180110 20:54]: > When more than one GP timers are used as kernel system timers and the > corresponding nodes in device-tree are marked with the same "disabled" > property, then the "attr" field of the property will be initialized > more than once as the property

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

* Qi Hou [180110 20:54]: > When more than one GP timers are used as kernel system timers and the > corresponding nodes in device-tree are marked with the same "disabled" > property, then the "attr" field of the property will be initialized > more than once as the property being added to sys file

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

On 1/13/2018 2:47 AM, Grygorii Strashko wrote: On 01/12/2018 03:08 PM, Tony Lindgren wrote: * Grygorii Strashko [180112 20:36]: Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

On 1/13/2018 2:47 AM, Grygorii Strashko wrote: On 01/12/2018 03:08 PM, Tony Lindgren wrote: * Grygorii Strashko [180112 20:36]: Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in device-tree are marked

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

On 01/12/2018 03:08 PM, Tony Lindgren wrote: * Grygorii Strashko [180112 20:36]: Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in device-tree are marked with the same "disabled"

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

On 01/12/2018 03:08 PM, Tony Lindgren wrote: * Grygorii Strashko [180112 20:36]: Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in device-tree are marked with the same "disabled" property, then the "attr"

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

* Grygorii Strashko [180112 20:36]: > Hi > > On 01/10/2018 10:54 PM, Qi Hou wrote: > > When more than one GP timers are used as kernel system timers and the > > corresponding nodes in device-tree are marked with the same "disabled" > > property, then the "attr" field of

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

* Grygorii Strashko [180112 20:36]: > Hi > > On 01/10/2018 10:54 PM, Qi Hou wrote: > > When more than one GP timers are used as kernel system timers and the > > corresponding nodes in device-tree are marked with the same "disabled" > > property, then the "attr" field of the property will be

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in device-tree are marked with the same "disabled" property, then the "attr" field of the property will be initialized more than once as the property being added to

Re: [PATCH, v3] arm: omap2: timer: fix a kmemleak caused in omap_get_timer_dt

Hi On 01/10/2018 10:54 PM, Qi Hou wrote: When more than one GP timers are used as kernel system timers and the corresponding nodes in device-tree are marked with the same "disabled" property, then the "attr" field of the property will be initialized more than once as the property being added to