From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: tegra: add Acer Chromebook 13 device tree
Date: Wed, 20 Aug 2014 16:32:02 +0200 [thread overview]
Message-ID: <20140820143201.GA3368@ulmo> (raw)
In-Reply-To: <CAOesGMhBdQh_ddycZ-Y5dupR9hW74bogHtG3yyPUJ2tAgWi19A@mail.gmail.com>
On Wed, Aug 20, 2014 at 06:29:14AM -0700, Olof Johansson wrote:
> On Mon, Aug 18, 2014 at 4:43 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
[...]
> > 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>
next prev parent reply other threads:[~2014-08-20 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 19:14 [PATCH v2] ARM: tegra: add Acer Chromebook 13 device tree Dylan Reid
2014-08-16 15:20 ` Andreas Färber
2014-08-18 16:10 ` Stephen Warren
2014-08-18 17:03 ` Andreas Färber
2014-08-18 23:24 ` Andrew Bresticker
2014-08-18 23:43 ` Stephen Warren
2014-08-19 0:11 ` Andrew Bresticker
2014-08-19 21:47 ` Stephen Warren
2014-08-20 5:36 ` Thierry Reding
2014-08-20 13:37 ` Olof Johansson
2014-08-20 15:25 ` Thierry Reding
2014-08-20 17:25 ` Andrew Bresticker
2014-08-20 13:29 ` Olof Johansson
2014-08-20 14:32 ` Thierry Reding [this message]
2014-08-20 15:40 ` Olof Johansson
2014-08-21 7:19 ` Thierry Reding
2014-08-18 23:05 ` Andrew Bresticker
2014-09-04 19:40 ` Stephen Warren
2014-09-04 20:33 ` Dylan Reid
2014-09-04 21:04 ` Stephen Warren
2014-09-04 21:08 ` Dylan Reid
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=20140820143201.GA3368@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).