From: jdl@jdl•com (Jon Loeliger)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 00/15] Device Tree schemas and validation
Date: Wed, 02 Oct 2013 08:22:58 -0500 [thread overview]
Message-ID: <E1VRMOI-0006iA-TF@jdl.com> (raw)
In-Reply-To: <524BE66D.7060308@baylibre.com>
> >
> > Benoit,
> >
> > Sorry, I meant to ask earlier but forgot.
> > Shouldn't this development be based on the
> > upstream DTC repository and not the in-kernel
> > copy of the DTC?
>
> Eventually, yes,
We should *start* there, though.
> but here the main point is to discuss the schema that
> will be used to defined bindings.
> In that case, the DTC patches code are mostly a proof of concept
Sure; all that is fine.
> using the Linux kernel as example.
Example?(*) We shouldn't churn the kernel.
jdl
(*) In the sense that *this* Universe is just
one example from all known Universes? :-)
next prev parent reply other threads:[~2013-10-02 13:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 16:52 [RFC 00/15] Device Tree schemas and validation Benoit Cousson
2013-10-01 8:06 ` Benoit Cousson
2013-10-01 13:17 ` Rob Herring
2013-10-01 15:06 ` Benoit Cousson
2013-10-01 15:17 ` Jon Loeliger
2013-10-02 8:24 ` David Gibson
2013-10-02 9:25 ` Benoit Cousson
2013-10-02 13:22 ` Jon Loeliger [this message]
2013-10-01 20:54 ` Rob Herring
2013-10-02 13:54 ` David Gibson
2013-10-02 18:08 ` Mark Brown
2013-10-02 23:38 ` David Gibson
2013-10-03 6:52 ` Benoit Cousson
2013-10-02 13:52 ` David Gibson
2013-10-01 22:22 ` Stephen Warren
2013-10-02 14:29 ` David Gibson
2013-10-03 13:53 ` Benoit Cousson
2013-10-06 3:02 ` Chaiken, Alison
2013-10-03 13:17 ` Benoit Cousson
[not found] ` <1380041541-17529-2-git-send-email-bcousson@baylibre.com>
2013-10-02 12:59 ` [RFC 01/15] scripts/dtc: fix most memory leaks in dtc David Gibson
[not found] ` <CAOwMV_zAZG3vvWS6pkyK-FbOEg_32KRO-k1SmFSh-pc9+0JiPA@mail.gmail.com>
2013-10-03 14:26 ` Fabien Parent
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=E1VRMOI-0006iA-TF@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.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