All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Bonesio <bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: dts and dtsi files on which I tested the syntax for my recent patch set.
Date: Wed, 20 Oct 2010 19:08:36 -0700	[thread overview]
Message-ID: <1287626916.4535.1511.camel@riker> (raw)
In-Reply-To: <20101020234638.GB10250-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>

On Wed, 2010-10-20 at 17:46 -0600, Grant Likely wrote:
> On Wed, Oct 20, 2010 at 03:22:17PM -0700, John Bonesio wrote:
> > Hi,
> > 
> > I have attached the two file I've used to test the new syntax from my
> > patch set. These might help get a feel for how the syntax and the
> > features work.
> 
> heh, what you should actually do (because you have to anyway) is add
> testcases for the new features to dtc in the tests directory.  'make
> check' runs the test cases.
> 
> > /remove-node/ &{soc/serial@2400};                  /* an example of using a label rooted path */
> 
> As previously mentioned by David, this conflicts with the already
> established convention of a path that does not start with a '/' means
> use a value from the /aliases node.  That ambiguity needs to
> be avoided, so the syntax still needs some massaging.

I think we should explore this a bit further. I just don't see in the
lexer code where it would parse anything with the syntax
&{alias/node/path} (except for my recent patch).

I looked through the parser too, and it wasn't obvious where it would
match '&' directly.

Maybe I'm just missing it.

> 
> g.
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss

  parent reply	other threads:[~2010-10-21  2:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 22:22 dts and dtsi files on which I tested the syntax for my recent patch set John Bonesio
2010-10-20 23:46 ` Grant Likely
     [not found]   ` <20101020234638.GB10250-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-10-21  2:08     ` John Bonesio [this message]
2010-10-21  3:14       ` David Gibson
2010-10-21  5:06         ` John Bonesio
2010-10-21  5:40           ` Grant Likely
     [not found]             ` <20101021054024.GB2252-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-10-21  5:53               ` David Gibson
2010-10-21  3:11     ` David Gibson
2010-10-25  3:20 ` David Gibson

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=1287626916.4535.1511.camel@riker \
    --to=bones-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.