Thread (21 messages) 21 messages, 6 authors, 2014-09-04
STALE4303d

[PATCH v2] ARM: tegra: add Acer Chromebook 13 device tree

From: Thierry Reding <hidden>
Date: 2014-08-20 14:32:02
Also in: linux-tegra

On Wed, Aug 20, 2014 at 06:29:14AM -0700, Olof Johansson wrote:
On Mon, Aug 18, 2014 at 4:43 PM, Stephen Warren [off-list ref] wrote:
[...]
quoted
Again, this board *isn't* Nyan, so it should pretend that it is.
It is a derivative design of the nyan reference platform, and it is
compatible with it. It is perfectly fine to claim to be compatible
with it. I'm sorry, but you're just wrong here.
I guess that depends a little on how you define compatibility. I had
always assumed that the top-level compatible string would be a sort of
"checksum" over the rest of the content. Which, admittedly, makes it
kind of redundant. Compatibility could mean a lot of things. Does it
mean any kernel/DTB compatible with one device could run on any device
derived from it? Does compatibility mean it needs to provide full
functionality or is it still compatible if it runs at a reduced feature
set but doesn't "break" otherwise?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140820/882f6571/attachment.sig>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help