From: Paul Mackerras <paulus@samba•org>
To: Tom Rini <trini@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, g.liakhovetski@gmx•de,
Milton Miller <miltonm@bga•com>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Fri, 4 Aug 2006 14:49:00 +1000 [thread overview]
Message-ID: <17618.53692.364647.412406@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060803135440.GB3075@smtp.west.cox.net>
Tom Rini writes:
> But "content requirements change" isn't the same as "left things out of
> their tree". It sounds, and I haven't seen the changes, so I'm not
> certain that the meaning behind a field changed. Something like that
> should change the dt version.
I disagree. Strongly. The dt version relates to the representation
of the tree, not its content.
If we *have* to change the meaning of a property value in a particular
node in an incompatible way, then we can do something such as adding
another property to indicate what the interpretation of the first
property value should be. Usually it's possible to find a way around
the problem without resorting to that, though.
> New fields aren't a problem. Changing
> existing fields meaning in incompatible ways is a problem.
Only a minor, localized problem. Nothing worth changing the whole dt
version number for.
Paul.
next prev parent reply other threads:[~2006-08-04 4:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 9:32 RFC: Location for Device Tree Sources? Milton Miller
2006-08-03 13:54 ` Tom Rini
2006-08-03 16:30 ` Milton Miller
2006-08-04 4:49 ` Paul Mackerras [this message]
2006-08-04 17:54 ` Tom Rini
2006-08-04 23:29 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 20:32 Jon Loeliger
2006-08-01 21:00 ` Guennadi Liakhovetski
2006-08-01 21:01 ` Matthew McClintock
2006-08-02 0:35 ` Mark A. Greer
2006-08-02 0:42 ` Mark A. Greer
2006-08-02 1:12 ` Josh Boyer
2006-08-02 3:20 ` Grant Likely
2006-08-02 13:35 ` Kumar Gala
2006-08-02 16:38 ` Tom Rini
2006-08-02 18:09 ` Matthew McClintock
2006-08-02 18:16 ` Vitaly Bordug
2006-08-02 18:21 ` Tom Rini
2006-08-02 18:23 ` Jon Loeliger
2006-08-02 18:57 ` Tom Rini
2006-08-02 20:06 ` Kumar Gala
2006-08-03 14:49 ` Li Yang
2006-08-03 15:47 ` Li Yang
2006-08-02 18:24 ` Mark A. Greer
2006-08-02 18:23 ` Mark A. Greer
2006-08-02 18:21 ` Grant Likely
2006-08-02 18:49 ` Mark A. Greer
2006-08-02 19:03 ` Josh Boyer
2006-08-02 19:26 ` Kumar Gala
2006-08-02 18:22 ` Mark A. Greer
2006-08-02 18:22 ` Matthew McClintock
2006-08-02 18:42 ` Mark A. Greer
2006-08-02 18:25 ` Jon Loeliger
2006-08-02 18:34 ` Mark A. Greer
2006-08-02 18:41 ` Brent Cook
2006-08-02 18:51 ` Mark A. Greer
2006-08-03 0:35 ` Tom Rini
2006-08-02 3:35 ` Li Yang-r58472
2006-08-04 4:51 ` Paul Mackerras
2006-08-09 11:18 ` Benjamin Herrenschmidt
2006-08-09 12:56 ` Josh Boyer
2006-08-09 16:38 ` Mark A. Greer
2006-08-09 16:48 ` Jon Loeliger
2006-08-09 17:03 ` Mark A. Greer
2006-08-09 14:03 ` Wolfgang Denk
2006-08-09 16:05 ` Benjamin Herrenschmidt
2006-08-09 18:47 ` Andy Fleming
2006-08-09 19:17 ` Wolfgang Denk
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=17618.53692.364647.412406@cargo.ozlabs.ibm.com \
--to=paulus@samba$(echo .)org \
--cc=g.liakhovetski@gmx$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=miltonm@bga$(echo .)com \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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