From: Tom Rini <trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: /aliases node and valid property names
Date: Mon, 20 Mar 2017 07:21:55 -0400 [thread overview]
Message-ID: <20170320112155.GT19897@bill-the-cat> (raw)
In-Reply-To: <20170320052705.GB29814-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Mon, Mar 20, 2017 at 04:27:05PM +1100, David Gibson wrote:
> 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.
OK. So leave things alone, or add a sentence / example without (and
assume that this thread will be enough for anyone in the future who sees
the occasional alias without a number and wonders if that's valid) ?
Thanks!
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-03-20 11:21 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
[not found] ` <20170320052705.GB29814-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-03-20 11:21 ` Tom Rini [this message]
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=20170320112155.GT19897@bill-the-cat \
--to=trini-owpks81ov/fwk0htik3j/w@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@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 read-only IMAP folder(s) and NNTP newsgroup(s).