From: Frank Rowand <frowand.list@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: Overlay sugar syntax (was: Re: [PATCH v6 3/4] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes)
Date: Tue, 6 Mar 2018 18:42:04 -0800 [thread overview]
Message-ID: <52edd21d-de54-9612-e50a-8bc9b6d2c39d@gmail.com> (raw)
In-Reply-To: <20180307023031.GC3083@umbus.fritz.box>
On 03/06/18 18:30, David Gibson wrote:
> On Tue, Mar 06, 2018 at 01:40:20PM -0800, Frank Rowand wrote:
>> On 03/06/18 11:51, Frank Rowand wrote:
>>> On 03/06/18 04:30, Geert Uytterhoeven wrote:
< snip >
>>> And the patched dtc works for a dts file that I was trying to convert
>>> to sugar dts syntax
>>
>> < snip >
>>
>> I noticed that a space in "&{/}" is an error. I wanted to check whether
>> that was deliberate, or that the patch wasn't fully complete yet.
>
> That's essentially deliberate - it's not really related to this patch
> at all. The patch just re-uses the existing syntax for a "path
> reference". The whole thing is treated as a single token, hence, no
> spaces.
>
> It might be possible to change that, but it could introduce some
> complications when the path reference syntax is used in other places.
> So I'm disinclined to change it, unless there's a very strong reason
> to.
>
< snip >
No, please do not change. I just wanted to make sure I understood the
intended syntax.
BTW, thanks for all the time you've been putting into this recent stuff.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-03-07 2:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 8:05 Overlay sugar syntax (was: Re: [PATCH v6 3/4] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes) Geert Uytterhoeven
2018-03-06 3:54 ` David Gibson
2018-03-06 12:30 ` Geert Uytterhoeven
2018-03-06 14:07 ` David Gibson
2018-03-06 22:05 ` Rob Herring
2018-03-06 19:51 ` Frank Rowand
2018-03-06 21:40 ` Frank Rowand
2018-03-07 2:30 ` David Gibson
2018-03-07 2:42 ` Frank Rowand [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=52edd21d-de54-9612-e50a-8bc9b6d2c39d@gmail.com \
--to=frowand.list@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
/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).