* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-06-28 14:53 ` Kevin Hilman
0 siblings, 0 replies; 13+ messages in thread
From: Kevin Hilman @ 2017-06-28 14:53 UTC (permalink / raw)
To: Rob Herring, devicetree-u79uwXL29TY76Z2rM5mHXA
Cc: linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
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.
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"
--
2.9.3
--
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
^ permalink raw reply related [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-06-28 14:53 ` Kevin Hilman
0 siblings, 0 replies; 13+ messages in thread
From: Kevin Hilman @ 2017-06-28 14:53 UTC (permalink / raw)
To: linux-arm-kernel
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.
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"
--
2.9.3
^ permalink raw reply related [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-06-28 14:53 ` Kevin Hilman
0 siblings, 0 replies; 13+ messages in thread
From: Kevin Hilman @ 2017-06-28 14:53 UTC (permalink / raw)
To: linus-amlogic
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.
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"
--
2.9.3
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [PATCH] dt-bindings: amlogic: add unstable statement
2017-06-28 14:53 ` Kevin Hilman
(?)
@ 2017-06-28 15:39 ` Jerome Brunet
-1 siblings, 0 replies; 13+ messages in thread
From: Jerome Brunet @ 2017-06-28 15:39 UTC (permalink / raw)
To: Kevin Hilman, Rob Herring, devicetree-u79uwXL29TY76Z2rM5mHXA
Cc: linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-06-28 15:39 ` Jerome Brunet
0 siblings, 0 replies; 13+ messages in thread
From: Jerome Brunet @ 2017-06-28 15:39 UTC (permalink / raw)
To: linux-arm-kernel
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"
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-06-28 15:39 ` Jerome Brunet
0 siblings, 0 replies; 13+ messages in thread
From: Jerome Brunet @ 2017-06-28 15:39 UTC (permalink / raw)
To: linus-amlogic
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"
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] dt-bindings: amlogic: add unstable statement
2017-06-28 14:53 ` Kevin Hilman
(?)
@ 2017-07-05 14:20 ` Rob Herring
-1 siblings, 0 replies; 13+ messages in thread
From: Rob Herring @ 2017-07-05 14:20 UTC (permalink / raw)
To: Kevin Hilman
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On Wed, Jun 28, 2017 at 07:53:43AM -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.
s/inthe/in the/
>
> Signed-off-by: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
I've yet to see anyone remove an unstable tag and I'd rather see these
for individual bindings than for the platform as a whole. In the end,
it's a platform maintainers decision whether to accept compatibility
breakage regardless of some text that probably no one reads.
In any case,
Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
--
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-07-05 14:20 ` Rob Herring
0 siblings, 0 replies; 13+ messages in thread
From: Rob Herring @ 2017-07-05 14:20 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jun 28, 2017 at 07:53:43AM -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.
s/inthe/in the/
>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
I've yet to see anyone remove an unstable tag and I'd rather see these
for individual bindings than for the platform as a whole. In the end,
it's a platform maintainers decision whether to accept compatibility
breakage regardless of some text that probably no one reads.
In any case,
Acked-by: Rob Herring <robh@kernel.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-07-05 14:20 ` Rob Herring
0 siblings, 0 replies; 13+ messages in thread
From: Rob Herring @ 2017-07-05 14:20 UTC (permalink / raw)
To: linus-amlogic
On Wed, Jun 28, 2017 at 07:53:43AM -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.
s/inthe/in the/
>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
I've yet to see anyone remove an unstable tag and I'd rather see these
for individual bindings than for the platform as a whole. In the end,
it's a platform maintainers decision whether to accept compatibility
breakage regardless of some text that probably no one reads.
In any case,
Acked-by: Rob Herring <robh@kernel.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] dt-bindings: amlogic: add unstable statement
2017-07-05 14:20 ` Rob Herring
(?)
@ 2017-07-05 19:32 ` Maxime Ripard
-1 siblings, 0 replies; 13+ messages in thread
From: Maxime Ripard @ 2017-07-05 19:32 UTC (permalink / raw)
To: Rob Herring
Cc: Kevin Hilman, devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On Wed, Jul 05, 2017 at 09:20:15AM -0500, Rob Herring wrote:
> On Wed, Jun 28, 2017 at 07:53:43AM -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.
>
> s/inthe/in the/
>
> >
> > Signed-off-by: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> > ---
> > Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
>
> I've yet to see anyone remove an unstable tag and I'd rather see these
> for individual bindings than for the platform as a whole. In the end,
> it's a platform maintainers decision whether to accept compatibility
> breakage regardless of some text that probably no one reads.
So what is the policy exactly to decide whether this statement can be
merged or not?
We have all the issues mentionned above, no backing from the vendor,
and yet, we were forced last year to bow down to one single "user"
without a clear usage into supporting a stable ABI that we never
really anticipated. How does that work exactly?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-07-05 19:32 ` Maxime Ripard
0 siblings, 0 replies; 13+ messages in thread
From: Maxime Ripard @ 2017-07-05 19:32 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jul 05, 2017 at 09:20:15AM -0500, Rob Herring wrote:
> On Wed, Jun 28, 2017 at 07:53:43AM -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.
>
> s/inthe/in the/
>
> >
> > Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> > ---
> > Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
>
> I've yet to see anyone remove an unstable tag and I'd rather see these
> for individual bindings than for the platform as a whole. In the end,
> it's a platform maintainers decision whether to accept compatibility
> breakage regardless of some text that probably no one reads.
So what is the policy exactly to decide whether this statement can be
merged or not?
We have all the issues mentionned above, no backing from the vendor,
and yet, we were forced last year to bow down to one single "user"
without a clear usage into supporting a stable ABI that we never
really anticipated. How does that work exactly?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170705/3a5d9b5e/attachment.sig>
^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH] dt-bindings: amlogic: add unstable statement
@ 2017-07-05 19:32 ` Maxime Ripard
0 siblings, 0 replies; 13+ messages in thread
From: Maxime Ripard @ 2017-07-05 19:32 UTC (permalink / raw)
To: linus-amlogic
On Wed, Jul 05, 2017 at 09:20:15AM -0500, Rob Herring wrote:
> On Wed, Jun 28, 2017 at 07:53:43AM -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.
>
> s/inthe/in the/
>
> >
> > Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> > ---
> > Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
>
> I've yet to see anyone remove an unstable tag and I'd rather see these
> for individual bindings than for the platform as a whole. In the end,
> it's a platform maintainers decision whether to accept compatibility
> breakage regardless of some text that probably no one reads.
So what is the policy exactly to decide whether this statement can be
merged or not?
We have all the issues mentionned above, no backing from the vendor,
and yet, we were forced last year to bow down to one single "user"
without a clear usage into supporting a stable ABI that we never
really anticipated. How does that work exactly?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20170705/3a5d9b5e/attachment.sig>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] dt-bindings: amlogic: add unstable statement
2017-07-05 19:32 ` Maxime Ripard
(?)
(?)
@ 2017-07-07 13:24 ` Rob Herring
-1 siblings, 0 replies; 13+ messages in thread
From: Rob Herring @ 2017-07-07 13:24 UTC (permalink / raw)
To: Maxime Ripard; +Cc: Kevin Hilman, devicetree, linux-arm-kernel, linux-amlogic
On Wed, Jul 5, 2017 at 2:32 PM, Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> On Wed, Jul 05, 2017 at 09:20:15AM -0500, Rob Herring wrote:
>> On Wed, Jun 28, 2017 at 07:53:43AM -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.
>>
>> s/inthe/in the/
>>
>> >
>> > Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>> > ---
>> > Documentation/devicetree/bindings/arm/amlogic.txt | 12 ++++++++++++
>> > 1 file changed, 12 insertions(+)
>>
>> I've yet to see anyone remove an unstable tag and I'd rather see these
>> for individual bindings than for the platform as a whole. In the end,
>> it's a platform maintainers decision whether to accept compatibility
>> breakage regardless of some text that probably no one reads.
>
> So what is the policy exactly to decide whether this statement can be
> merged or not?
I acked it, didn't I?
> We have all the issues mentionned above, no backing from the vendor,
> and yet, we were forced last year to bow down to one single "user"
> without a clear usage into supporting a stable ABI that we never
> really anticipated. How does that work exactly?
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2017-07-07 13:24 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
[not found] ` <20170628145343.25443-1-khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-06-28 15:39 ` Jerome Brunet
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
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.