From: Neil Armstrong <neil.armstrong@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-amlogic@lists.infradead.org"
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH 1/2] dt-bindings: arm: amlogic: remove unstable remark
Date: Mon, 26 Feb 2024 09:20:27 +0100 [thread overview]
Message-ID: <7d9221e0-8165-422b-abbb-e1566a7a733e@linaro.org> (raw)
In-Reply-To: <20240224084030.5867-1-krzysztof.kozlowski@linaro.org>
+ linux-amlogic@lists.infradead.org
On 24/02/2024 09:40, Krzysztof Kozlowski wrote:
> Amlogic bindings were marked as work-in-progress / unstable in 2017 in
> commit 7e8634e821e1 ("dt-bindings: amlogic: add unstable statement").
> Almost seven years is enough, so drop the "unstable" remark and expect
> usual ABI rules.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> Documentation/devicetree/bindings/arm/amlogic.yaml | 11 -----------
> 1 file changed, 11 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic.yaml b/Documentation/devicetree/bindings/arm/amlogic.yaml
> index ce0ea36de0c0..edbc21159588 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic.yaml
> +++ b/Documentation/devicetree/bindings/arm/amlogic.yaml
> @@ -9,17 +9,6 @@ title: Amlogic SoC based Platforms
> maintainers:
> - Kevin Hilman <khilman@baylibre.com>
>
> -description: |+
> - Work in progress statement:
> -
> - Device tree files and bindings applying to Amlogic SoCs and boards are
> - considered "unstable". Any Amlogic device tree binding may change at
> - any time. Be sure to use a device tree binary and a kernel image
> - generated from the same source tree.
> -
> - Please refer to Documentation/devicetree/bindings/ABI.rst for a definition of a
> - stable binding/ABI.
> -
> properties:
> $nodename:
> const: '/'
Acked-by: Neil Armstrong <neil.armstrong@linaro.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next parent reply other threads:[~2024-02-26 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240224084030.5867-1-krzysztof.kozlowski@linaro.org>
2024-02-26 8:20 ` Neil Armstrong [this message]
2024-02-26 22:04 ` [PATCH 1/2] dt-bindings: arm: amlogic: remove unstable remark Martin Blumenstingl
[not found] ` <20240224084030.5867-2-krzysztof.kozlowski@linaro.org>
2024-02-26 8:20 ` [PATCH 2/2] dt-bindings: arm: amlogic: add Neil, Martin and Jerome as maintainers Neil Armstrong
2024-02-26 22:05 ` Martin Blumenstingl
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=7d9221e0-8165-422b-abbb-e1566a7a733e@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).