Re: [PATCH] clk: Provide !COMMON_CLK dummy for devm_clk_rate_exclusive_get()

[Stephen Boyd]

Quoting Uwe Kleine-König (2024-04-19 13:00:19)
> Hello Stephen,
> 
> On Fri, Apr 12, 2024 at 10:49:35PM +0200, Uwe Kleine-K�nig wrote:
> > On Thu, Mar 28, 2024 at 03:35:57PM -0700, Stephen Boyd wrote:
> > > Quoting Uwe Kleine-K�nig (2024-03-27 00:33:10)
> > > > To be able to compile drivers using devm_clk_rate_exclusive_get() also
> > > > on platforms without the common clk framework, add a dummy
> > > > implementation that does the same as clk_rate_exclusive_get() in that
> > > > case (i.e. nothing).
> > > > 
> > > > Reported-by: kernel test robot <lkp@xxxxxxxxx>
> > > > Closes: https://lore.kernel.org/oe-kbuild-all/202403270305.ydvX9xq1-lkp@xxxxxxxxx/
> > > > Fixes: b0cde62e4c54 ("clk: Add a devm variant of clk_rate_exclusive_get()")
> > > > Signed-off-by: Uwe Kleine-K�nig <u.kleine-koenig@xxxxxxxxxxxxxx>
> > > > ---
> > > 
> > > Applied to clk-fixes
> > 
> > I assume that means it will be sent to Linus before 6.9? That would be
> > great because I want to make use of this function in some drivers and
> > the build bots nag about my for-next branch that in some configurations
> > this function is missing.

Yes.

> 
> Gentle ping. I'd like to get the patches I intend to send to Linus for
> v6.10-rc1 into shape. To have these unmodified in my for-next branch for
> some time it would be great to know your plans for the clk-fixes branch. 
> Alternatively: Can I expect the commit not to be changed any more and
> pull it into my pwm tree?
> 

clk-fixes is sent to Linus during the rc cycle. I'm sending a PR today.