public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	Pantelis Antoniou <panto@antoniou-consulting.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] of: convert unittest overlay devicetree source to sugar syntax
Date: Mon, 29 Jan 2018 16:14:45 -0800	[thread overview]
Message-ID: <f3af3f81-da51-6534-2ebd-0adf88677d47@gmail.com> (raw)
In-Reply-To: <CAMuHMdVSDj2MmTzbxgZeBx94EKdcRr6B_3Bh+Mb35XhBRPPGXw@mail.gmail.com>

On 01/29/18 02:37, Geert Uytterhoeven wrote:
> Hi Frank,
> 
> On Mon, Jan 29, 2018 at 3:53 AM,  <frowand.list@gmail.com> wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> The unittest-data overlays have been pulled into proper overlay
>> devicetree source files without changing their format.  The
>> next step is to convert them to use sugar syntax instead of
>> hand coding overlay fragments structure.
> 
> Cool! I had heard about the new syntax, but hadn't realized it was merged in
> v4.15-rc1.
> 
> Have you used your overlay_convert_old_to_new script to convert them?
> 
>> A few of the overlays can not be converted because they test
>> absolute target paths in the overlay fragment.  dtc does not
>> generate this type of target:
>>   overlay_0.dts
>>   overlay_1.dts
>>   overlay_12.dts
>>   overlay_13.dts
> 
> And I guess you want to keep at least a few tests using the non-sugar syntax
> anyway?

Not really.  But not something I care about at the moment.


> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> 

  reply	other threads:[~2018-01-30  0:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  2:53 [PATCH 0/2] of: change overlay apply input data from EDT to FDT frowand.list
2018-01-29  2:53 ` [PATCH 1/2] " frowand.list
2018-01-29  3:21   ` Masahiro Yamada
2018-01-29  8:12     ` Frank Rowand
2018-01-29 14:42   ` Rob Herring
2018-01-29 15:05     ` Geert Uytterhoeven
2018-01-30  0:13       ` Frank Rowand
2018-01-30  0:01     ` Frank Rowand
2018-02-05  6:07       ` Rob Herring
2018-01-29  2:53 ` [PATCH 2/2] of: convert unittest overlay devicetree source to sugar syntax frowand.list
2018-01-29 10:37   ` Geert Uytterhoeven
2018-01-30  0:14     ` Frank Rowand [this message]
2018-01-29 14:08 ` [PATCH 0/2] of: change overlay apply input data from EDT to FDT Geert Uytterhoeven
2018-01-30  0:22   ` Frank Rowand
2018-01-30  0:35     ` Frank Rowand
2018-01-30 16:28       ` Alan Tull

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=f3af3f81-da51-6534-2ebd-0adf88677d47@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=panto@antoniou-consulting.com \
    --cc=robh+dt@kernel.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