devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <tom.rini@gmail.com>
To: devicetree@vger.kernel.org
Subject: [RFC] Best practices for hardware shipping device trees
Date: Wed, 14 Aug 2013 11:13:45 -0400	[thread overview]
Message-ID: <20130814151345.GA2983@bill-the-cat> (raw)

Hey all,

Do we have a document yet talking about the best practices for how we
would like a hardware vendor to ship, store and possibly update a device
tree, on the hardware?  "However they like" seems likely to invite
problems down the line with everyone trying their own thing.  Thanks!

-- 
Tom

             reply	other threads:[~2013-08-14 15:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 15:13 Tom Rini [this message]
2013-08-14 16:38 ` [RFC] Best practices for hardware shipping device trees Jason Cooper
2013-08-14 18:41   ` Tom Rini
2013-08-14 18:53     ` Jason Cooper
2013-08-14 16:44 ` Stephen Warren
2013-08-14 17:20   ` Jason Cooper
2013-08-14 18:25   ` Tom Rini
2013-08-15  0:37     ` Nicolas Pitre
2013-08-15  2:09       ` Tom Rini
2013-08-15  2:57         ` Nicolas Pitre
2013-08-15 14:53           ` Tom Rini
2013-08-15 15:30             ` Stephen Warren
2013-08-15 16:37               ` Tom Rini
2013-08-15 17:31                 ` Stephen Warren
2013-08-15 18:56                   ` Tom Rini
2013-08-15 22:34                     ` Stephen Warren
2013-08-15 15:45             ` Nicolas Pitre
2013-08-15 17:00               ` Tom Rini
2013-08-15 23:59           ` David Gibson
2013-08-16  2:51             ` Nicolas Pitre
2013-08-19  0:15               ` David Gibson
2013-08-19 18:43                 ` Nicolas Pitre
2013-08-20  6:40                   ` Alexander Graf
2013-08-20 12:02                     ` Nicolas Pitre
2013-08-20 17:02                       ` Matt Sealey
2013-08-20 17:29                         ` Nicolas Pitre
2013-08-20 15:03                     ` Tom Rini

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=20130814151345.GA2983@bill-the-cat \
    --to=tom.rini@gmail.com \
    --cc=devicetree@vger.kernel.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).