LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca
To: linuxppc-dev@ozlabs.org, paulus@samba.org, tnt@246tnt.com
Subject: [PATCH] [POWERPC] Make it blatently clear; 5200 device tree is not yet stable
Date: Sat, 13 Jan 2007 16:58:19 -0700	[thread overview]
Message-ID: <11687326992407-git-send-email-grant.likely@secretlab.ca> (raw)

From: Grant Likely <grant.likely@secretlab.ca>

---
Paulus,

Please apply for 2.6.20.  This is documentation only, but I don't want
to give people false assumptions about the stability of the 5200 device
tree bindings

 .../powerpc/mpc52xx-device-tree-bindings.txt       |    9 +++++++++
 arch/powerpc/boot/dts/lite5200.dts                 |    8 ++++++++
 arch/powerpc/boot/dts/lite5200b.dts                |    8 ++++++++
 3 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/Documentation/powerpc/mpc52xx-device-tree-bindings.txt b/Documentation/powerpc/mpc52xx-device-tree-bindings.txt
index 7fb3b8a..e90efe3 100644
--- a/Documentation/powerpc/mpc52xx-device-tree-bindings.txt
+++ b/Documentation/powerpc/mpc52xx-device-tree-bindings.txt
@@ -4,6 +4,15 @@ MPC52xx Device Tree Bindings
 (c) 2006 Secret Lab Technologies Ltd
 Grant Likely <grant.likely at secretlab.ca>
 
+********** DRAFT ***********
+* WARNING: Do not depend on definiton remaining static between
+* kernel versions.  The 5200 device tree conventions are still in flux
+* and could change without notice.  Keep an eye on the linuxppc-dev
+* mailing list for more details
+*
+* Hopefully by 2.6.21 it will be stable.  ---gcl, Jan 13, 2007
+********** DRAFT ***********
+
 I - Introduction
 ================
 Boards supported by the arch/powerpc architecture require device tree be
diff --git a/arch/powerpc/boot/dts/lite5200.dts b/arch/powerpc/boot/dts/lite5200.dts
index a8efb59..e953568 100644
--- a/arch/powerpc/boot/dts/lite5200.dts
+++ b/arch/powerpc/boot/dts/lite5200.dts
@@ -10,6 +10,14 @@
  * option) any later version.
  */
 
+/*
+ * WARNING: Do not depend on this tree remaining static between
+ * kernel versions.  The 5200 device tree conventions are still in flux
+ * and could change without notice.
+ *
+ * Hopefully by 2.6.21 it will be stable.  ---gcl, Jan 13, 2007
+ */
+
 / {
 	model = "Lite5200";
 	compatible = "lite5200\0lite52xx\0mpc5200\0mpc52xx";
diff --git a/arch/powerpc/boot/dts/lite5200b.dts b/arch/powerpc/boot/dts/lite5200b.dts
index 1aabee4..c3123be 100644
--- a/arch/powerpc/boot/dts/lite5200b.dts
+++ b/arch/powerpc/boot/dts/lite5200b.dts
@@ -10,6 +10,14 @@
  * option) any later version.
  */
 
+/*
+ * WARNING: Do not depend on this tree remaining static between
+ * kernel versions.  The 5200 device tree conventions are still in flux
+ * and could change without notice.
+ *
+ * Hopefully by 2.6.21 it will be stable.  ---gcl, Jan 13, 2007
+ */
+
 / {
 	model = "Lite5200b";
 	compatible = "lite5200b\0lite52xx\0mpc5200b\0mpc52xx";
-- 
1.4.3.rc2.g0503

             reply	other threads:[~2007-01-13 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 23:58 grant.likely [this message]
2007-01-14  0:31 ` [PATCH] [POWERPC] Make it blatently clear; 5200 device tree is not yet stable Segher Boessenkool
2007-01-14  0:42   ` Grant Likely
2007-01-14  0:53     ` Segher Boessenkool

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=11687326992407-git-send-email-grant.likely@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tnt@246tnt.com \
    /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