lkml.org 
[lkml]   [2019]   [Dec]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 0/3] clk: let clock perform allocation in init
From
Date
Quoting Jerome Brunet (2019-11-29 07:36:28)
>
> On Tue 24 Sep 2019 at 14:39, Jerome Brunet <jbrunet@baylibre.com> wrote:
>
> > This patchset is a follow up on this pinky swear [0].
> > Its purpose is:
> > * Clarify the acceptable use of clk_ops init() callback
> > * Let the init() callback return an error code in case anything
> > fail.
> > * Add the terminate() counter part of of init() to release the
> > resources which may have been claimed in init()
> >
> > After discussing with Stephen at LPC, I decided to drop the 2 last patches
> > of the RFC [1]. I can live without it for now and nobody expressed a
> > critical need to get the proposed placeholder.
> >
> > [0]: https://lkml.kernel.org/r/CAEG3pNB-143Pr_xCTPj=tURhpiTiJqi61xfDGDVdU7zG5H-2tA@mail.gmail.com
> > [1]: https://lkml.kernel.org/r/20190828102012.4493-1-jbrunet@baylibre.com
> >
>
> Hi Stephen,
>
> Do you think we can fit this into the incoming cycle ?
>

Sorry I missed this one. I'll apply it soon but won't be for this merge
window.

\
 
 \ /
  Last update: 2019-12-03 10:06    [W:0.142 / U:1.636 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site