devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David VomLehn <dvomlehn-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Device Tree Mailing List
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Subnodes of vendor-added nodes
Date: Mon, 19 Sep 2011 21:37:35 -0700	[thread overview]
Message-ID: <20110920043735.GA25354@dvomlehn-lnx2.corp.sa.net> (raw)

I know the device tree has a protocol for vendors to extend the types of nodes without
causing namespace collisions, e.g. acme,explosives. Do subnodes and properties of the
extended nodes also need the leading <vendor> and comma?
-- 
David VL

             reply	other threads:[~2011-09-20  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  4:37 David VomLehn [this message]
     [not found] ` <20110920043735.GA25354-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2011-09-20  4:53   ` Subnodes of vendor-added nodes Grant Likely
2011-09-20  4:58   ` David Gibson
     [not found]     ` <20110920045816.GK29197-787xzQ0H9iQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2011-09-20  5:01       ` Grant Likely

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=20110920043735.GA25354@dvomlehn-lnx2.corp.sa.net \
    --to=dvomlehn-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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).