From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: clock: ti: remove unstable remark
Date: Thu, 29 Feb 2024 07:48:10 +0200 [thread overview]
Message-ID: <20240229054810.GG52537@atomide.com> (raw)
In-Reply-To: <2df72cc0d2be877c1f6eda8ebcf79508.sboyd@kernel.org>
* Stephen Boyd <sboyd@kernel.org> [240228 22:59]:
> +Tony
>
> Quoting Krzysztof Kozlowski (2024-02-24 01:12:35)
> > Several TI SoC clock bindings were marked as work-in-progress / unstable
> > between 2013-2016, for example in commit f60b1ea5ea7a ("CLK: TI: add
> > support for gate clock"). It was enough of time to consider them stable
> > and expect usual ABI rules.
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > ---
>
> Acked-by: Stephen Boyd <sboyd@kernel.org>
Makes sense to me:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2024-02-29 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 9:12 [PATCH 1/3] dt-bindings: clock: keystone: remove unstable remark Krzysztof Kozlowski
2024-02-24 9:12 ` [PATCH 2/3] dt-bindings: clock: ti: " Krzysztof Kozlowski
2024-02-26 19:45 ` Rob Herring
2024-02-28 22:59 ` Stephen Boyd
2024-02-29 5:48 ` Tony Lindgren [this message]
2024-02-24 9:12 ` [PATCH 3/3] dt-bindings: remoteproc: ti,davinci: " Krzysztof Kozlowski
2024-02-26 16:12 ` Mathieu Poirier
2024-02-26 19:45 ` Rob Herring
2024-02-26 19:44 ` [PATCH 1/3] dt-bindings: clock: keystone: " Rob Herring
2024-02-28 23:00 ` Stephen Boyd
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=20240229054810.GG52537@atomide.com \
--to=tony@atomide.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/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.