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

On 2018年01月09日 19:52, Ladislav Michl wrote: On Tue, Jan 09, 2018 at 05:24:21PM +0800, 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 w

Re: [RFC] dmaengine: pl330: fix a race condition in case of threaded irqs

Hi, Jassi Brar On 2018年01月09日 16:29, Jassi Brar wrote: On Mon, Dec 25, 2017 at 7:50 AM, Qi Hou wrote: > I found this problem below, and I now understand why it happens, but I'm not > 100% sure what is the best way to fix it. > > When booting up with "threadirqs" in command line, all irq handle

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

On 2018年01月09日 07:13, kbuild test robot wrote: Hi Qi, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on omap/for-next] [also build test WARNING on v4.15-rc7 next-20180108] [if your patch is applied to the wrong git tree, please drop us a note to help improve

Re: [PATCH] lockdep: call time_hardirqs_off after clearing hardirqs_enabled

Hi, all Sorry for everybody concerned. Please ignore this patch. I sent this patch without my supervisor's ACKed. I missed a lot of important information. I'm a newbie for submitting patches to community and I should have sent a valid patch under my supervisor's guidance. Execuse me, ever

Re: [PATCH] lockdep: call trace_hardirqs_off after clearing hardirqs_enabled

On 2017年03月13日 22:05, Steven Rostedt wrote: On Mon, 13 Mar 2017 18:08:48 +0800 Qi Hou wrote: The current order of calls within trace_hardirqs_off() would provoke an "unannotated irqs-off" WARNING. This warning was reported by check_flags() when it found that the hardirqs has been disabled b