From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Alexandre Courbot
<acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Device tree node names
Date: Fri, 17 Aug 2012 12:36:11 +0100 [thread overview]
Message-ID: <20120817113610.GB32216@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <502D67DF.7010605-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
On Thu, Aug 16, 2012 at 11:36:31AM -1000, Mitch Bradley wrote:
> The main "rule" for node names is that a user browsing the device tree
> can easily determine what something is. Thus "ethernet" instead of
> "DEC,21140".
Does this actually buy us much? It seems like it's something that's
much better addressed through comments in the device tree than with
syntax.
next prev parent reply other threads:[~2012-08-17 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 19:34 Device tree node names Stephen Warren
[not found] ` <502D4B28.4020108-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-16 21:36 ` Mitch Bradley
[not found] ` <502D67DF.7010605-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-08-17 11:36 ` Mark Brown [this message]
[not found] ` <20120817113610.GB32216-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-08-17 13:10 ` Mitch Bradley
2012-08-22 15:19 ` Stephen Warren
[not found] ` <5034F870.2010604-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-22 18:20 ` Rob Herring
2012-08-16 21:46 ` Associating devices with multiple parents Mitch Bradley
[not found] ` <502D6A3A.7060808-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-08-16 22:20 ` Grant Likely
[not found] ` <CACxGe6uqWG7kRUL0o3qPCMDvG52UyqTMez+AT1yK55X-xgaRuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-17 10:37 ` Mark Brown
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=20120817113610.GB32216@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=wmb-D5eQfiDGL7eakBO8gow8eQ@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).