From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] dt-bindings: amlogic: add unstable statement
Date: Wed, 28 Jun 2017 17:39:34 +0200 [thread overview]
Message-ID: <1498664374.2337.7.camel@baylibre.com> (raw)
In-Reply-To: <20170628145343.25443-1-khilman@baylibre.com>
On Wed, 2017-06-28 at 07:53 -0700, Kevin Hilman wrote:
> Due to the lack of documentation on this SoC family, discovery of new
> features, and correcting of previous misunderstandings is expected, so
> it's unrealistic to expect any form of stable bindings for this SoC
> family.??Make that clear inthe binding documentation.
>
Acked-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> ?Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> ?1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
> b/Documentation/devicetree/bindings/arm/amlogic.txt
> index bfd5b558477d..9be902b4656d 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
> @@ -1,6 +1,18 @@
> ?Amlogic MesonX device tree bindings
> ?-------------------------------------------
> ?
> +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.txt for a definition of
> a
> +stable binding/ABI.
> +
> +---------------------------------------------------------------
> +
> ?Boards with the Amlogic Meson6 SoC shall have the following properties:
> ???Required root node property:
> ?????compatible: "amlogic,meson6"
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-bindings: amlogic: add unstable statement
Date: Wed, 28 Jun 2017 17:39:34 +0200 [thread overview]
Message-ID: <1498664374.2337.7.camel@baylibre.com> (raw)
In-Reply-To: <20170628145343.25443-1-khilman@baylibre.com>
On Wed, 2017-06-28 at 07:53 -0700, Kevin Hilman wrote:
> Due to the lack of documentation on this SoC family, discovery of new
> features, and correcting of previous misunderstandings is expected, so
> it's unrealistic to expect any form of stable bindings for this SoC
> family.??Make that clear inthe binding documentation.
>
Acked-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> ?Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> ?1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
> b/Documentation/devicetree/bindings/arm/amlogic.txt
> index bfd5b558477d..9be902b4656d 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
> @@ -1,6 +1,18 @@
> ?Amlogic MesonX device tree bindings
> ?-------------------------------------------
> ?
> +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.txt for a definition of
> a
> +stable binding/ABI.
> +
> +---------------------------------------------------------------
> +
> ?Boards with the Amlogic Meson6 SoC shall have the following properties:
> ???Required root node property:
> ?????compatible: "amlogic,meson6"
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] dt-bindings: amlogic: add unstable statement
Date: Wed, 28 Jun 2017 17:39:34 +0200 [thread overview]
Message-ID: <1498664374.2337.7.camel@baylibre.com> (raw)
In-Reply-To: <20170628145343.25443-1-khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
On Wed, 2017-06-28 at 07:53 -0700, Kevin Hilman wrote:
> Due to the lack of documentation on this SoC family, discovery of new
> features, and correcting of previous misunderstandings is expected, so
> it's unrealistic to expect any form of stable bindings for this SoC
> family. Make that clear inthe binding documentation.
>
Acked-by: Jerome Brunet <jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> Signed-off-by: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
> b/Documentation/devicetree/bindings/arm/amlogic.txt
> index bfd5b558477d..9be902b4656d 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
> @@ -1,6 +1,18 @@
> Amlogic MesonX device tree bindings
> -------------------------------------------
>
> +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.txt for a definition of
> a
> +stable binding/ABI.
> +
> +---------------------------------------------------------------
> +
> Boards with the Amlogic Meson6 SoC shall have the following properties:
> Required root node property:
> compatible: "amlogic,meson6"
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-28 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 14:53 [PATCH] dt-bindings: amlogic: add unstable statement Kevin Hilman
2017-06-28 14:53 ` Kevin Hilman
2017-06-28 14:53 ` Kevin Hilman
2017-06-28 15:39 ` Jerome Brunet [this message]
2017-06-28 15:39 ` Jerome Brunet
2017-06-28 15:39 ` Jerome Brunet
2017-07-05 14:20 ` Rob Herring
2017-07-05 14:20 ` Rob Herring
2017-07-05 14:20 ` Rob Herring
2017-07-05 19:32 ` Maxime Ripard
2017-07-05 19:32 ` Maxime Ripard
2017-07-05 19:32 ` Maxime Ripard
2017-07-07 13:24 ` Rob Herring
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=1498664374.2337.7.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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.