devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Tom Rini <trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Cc: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: /aliases node and valid property names
Date: Mon, 20 Mar 2017 16:27:05 +1100	[thread overview]
Message-ID: <20170320052705.GB29814@umbus.fritz.box> (raw)
In-Reply-To: <20170318011906.GA19897@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Fri, Mar 17, 2017 at 09:19:06PM -0400, Tom Rini wrote:
> Hey all,
> 
> I found out about https://github.com/raspberrypi/firmware/issues/613 and
> in digging a little harder, this is not the first case where 'ethernet'
> has been added rather than 'ethernet0'.  Looking at the spec, it's
> implied (by all the examples) that property names end in a number but
> it's certainly allowable by the way things are worded to not.  Is it
> worth adding any further words here, another example, or just leaving
> everything alone?  Thanks!

Numbers shouldn't be required.  Certainly on old OF-era machines,
aliases called simply 'net' or 'disk' were both common and useful.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-03-20  5:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18  1:19 /aliases node and valid property names Tom Rini
2017-03-20  5:27 ` David Gibson [this message]
     [not found]   ` <20170320052705.GB29814-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-03-20 11:21     ` 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=20170320052705.GB29814@umbus.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=trini-OWPKS81ov/FWk0Htik3J/w@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).