From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] clk: let clock perform allocation in init
Date: Tue, 03 Dec 2019 01:05:15 -0800 [thread overview]
Message-ID: <20191203090516.1A03B20661@mail.kernel.org> (raw)
In-Reply-To: <1jv9r27kzn.fsf@starbuckisacylon.baylibre.com>
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.
next prev parent reply other threads:[~2019-12-03 9:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 12:39 [PATCH 0/3] clk: let clock perform allocation in init Jerome Brunet
2019-09-24 12:39 ` [PATCH 1/3] clk: actually call the clock init before any other callback of the clock Jerome Brunet
2019-12-24 2:59 ` Stephen Boyd
2019-09-24 12:39 ` [PATCH 2/3] clk: let init callback return an error code Jerome Brunet
2019-09-24 12:39 ` Jerome Brunet
2019-09-24 13:38 ` Ankur Tyagi
2019-09-24 13:38 ` Ankur Tyagi
2019-09-24 14:10 ` Jerome Brunet
2019-09-24 14:10 ` Jerome Brunet
2019-09-24 14:10 ` Jerome Brunet
2019-09-24 16:19 ` Andrew Lunn
2019-09-29 19:33 ` Heiko Stuebner
2019-09-29 19:33 ` Heiko Stuebner
2019-09-29 19:33 ` Heiko Stuebner
2019-12-24 2:59 ` Stephen Boyd
2019-12-24 2:59 ` Stephen Boyd
2019-09-24 12:39 ` [PATCH 3/3] clk: add terminate callback to clk_ops Jerome Brunet
2019-12-24 2:59 ` Stephen Boyd
2019-11-18 10:08 ` [PATCH 0/3] clk: let clock perform allocation in init Jerome Brunet
2019-11-29 15:36 ` Jerome Brunet
2019-12-03 9:05 ` Stephen Boyd [this message]
2019-12-16 9:17 ` Jerome Brunet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191203090516.1A03B20661@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.