Re: [PATCH] clk: Evict unregistered clks from parent caches

2019-08-28 Thread Stephen Boyd
Quoting kbuild test robot (2019-08-27 03:28:35) > Hi Stephen, > > I love your patch! Yet something to improve: > > [auto build test ERROR on linus/master] > [cannot apply to v5.3-rc6 next-20190827] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the

Re: [PATCH] clk: Evict unregistered clks from parent caches

2019-08-27 Thread kbuild test robot
Hi Stephen, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.3-rc6 next-20190827] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] clk: Evict unregistered clks from parent caches

2019-08-26 Thread Sai Prakash Ranjan
On 2019-08-27 05:13, Stephen Boyd wrote: We leave a dangling pointer in each clk_core::parents array that has an unregistered clk as a potential parent when that clk_core pointer is freed by clk{_hw}_unregister(). It is impossible for the true parent of a clk to be set with clk_set_parent() once

Re: [PATCH] clk: Evict unregistered clks from parent caches

2019-08-26 Thread Bjorn Andersson
On Mon 26 Aug 16:43 PDT 2019, Stephen Boyd wrote: > We leave a dangling pointer in each clk_core::parents array that has an > unregistered clk as a potential parent when that clk_core pointer is > freed by clk{_hw}_unregister(). It is impossible for the true parent of > a clk to be set with

[PATCH] clk: Evict unregistered clks from parent caches

2019-08-26 Thread Stephen Boyd
We leave a dangling pointer in each clk_core::parents array that has an unregistered clk as a potential parent when that clk_core pointer is freed by clk{_hw}_unregister(). It is impossible for the true parent of a clk to be set with clk_set_parent() once the dangling pointer is left in the cache