devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	linux-kernel@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	linux-remoteproc@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: clock: ti: remove unstable remark
Date: Mon, 26 Feb 2024 13:45:04 -0600	[thread overview]
Message-ID: <170897670414.1320059.18104874403341289968.robh@kernel.org> (raw)
In-Reply-To: <20240224091236.10146-2-krzysztof.kozlowski@linaro.org>


On Sat, 24 Feb 2024 10:12:35 +0100, Krzysztof Kozlowski wrote:
> 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>
> ---
>  Documentation/devicetree/bindings/clock/ti/adpll.txt            | 2 --
>  Documentation/devicetree/bindings/clock/ti/apll.txt             | 2 --
>  Documentation/devicetree/bindings/clock/ti/autoidle.txt         | 2 --
>  Documentation/devicetree/bindings/clock/ti/clockdomain.txt      | 2 --
>  Documentation/devicetree/bindings/clock/ti/composite.txt        | 2 --
>  Documentation/devicetree/bindings/clock/ti/divider.txt          | 2 --
>  Documentation/devicetree/bindings/clock/ti/dpll.txt             | 2 --
>  Documentation/devicetree/bindings/clock/ti/fapll.txt            | 2 --
>  .../devicetree/bindings/clock/ti/fixed-factor-clock.txt         | 2 --
>  Documentation/devicetree/bindings/clock/ti/gate.txt             | 2 --
>  Documentation/devicetree/bindings/clock/ti/interface.txt        | 2 --
>  Documentation/devicetree/bindings/clock/ti/mux.txt              | 2 --
>  12 files changed, 24 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2024-02-26 19:45 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 [this message]
2024-02-28 22:59   ` Stephen Boyd
2024-02-29  5:48     ` Tony Lindgren
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=170897670414.1320059.18104874403341289968.robh@kernel.org \
    --to=robh@kernel.org \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).