From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 0/2] r8a777[89] dtsi sorting
Date: Mon, 1 Sep 2014 10:34:44 +0900 [thread overview]
Message-ID: <20140901013444.GI32075@verge.net.au> (raw)
In-Reply-To: <20140901012420.GG32075@verge.net.au>
On Mon, Sep 01, 2014 at 10:24:21AM +0900, Simon Horman wrote:
> On Fri, Aug 29, 2014 at 10:03:27PM +0200, Geert Uytterhoeven wrote:
> > Hi Uli,
> >
> > On Fri, Aug 29, 2014 at 8:16 PM, Ulrich Hecht
> > <ulrich.hecht+renesas@gmail.com> wrote:
> > > These are the dtsi files for r8a7778 and r8a7779 sorted according to what I
> > > imagine to be accepted standards now: sort by address, "compatible" goes
> > > first, #include directives before anything else. The sorting was done using
> > > a little script I wrote (https://github.com/uli/dtssort).
> >
> > Nice! (but soon thereafter I got sidetracked by decomp ;-)
> >
> > > I chose these two files because the required changes are relatively small.
> > > Doing this for r8a779x yields a gargantuan and entirely unreadable patch due
> > > to the random shifting about of large blocks of code. If anybody knows a
> > > tool that makes such things somewhat manageable to review, please speak up.
> >
> > You more or less gave a solution at the top of your email: split it in multiple
> > patches: one to sort the includes, one to sort the properties inside the nodes,
> > and one single patch for each node you move.
> > Yes, too many patches, but good for the patch statistics ;-)
>
> FWIW, I would rather many small patches than one gargatuan one.
Also, please repost this thread with Olof Johansson CCed
(I have cced him on this reply. It was he who originally requested
the dts files be sorted. So I would value his opinion on the
order you have come up with.
>
> > Another approach could be to start considering SoCs as built from multiple
> > hardware blocks, not only at the hardware/software level, but also at the DTS
> > level. I.e. use macros to instantiate nodes. This makes it easier to avoid
> > stupid typos in e.g. the 5th i2c node. In addition, many SoCs are similar, and
> > only differ in a few nodes.
> >
> > 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
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-09-01 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:16 [PATCH 0/2] r8a777[89] dtsi sorting Ulrich Hecht
2014-08-29 18:16 ` [PATCH 1/2] ARM: shmobile: r8a7778 dtsi: sort it Ulrich Hecht
2014-08-29 18:16 ` [PATCH 2/2] ARM: shmobile: r8a7779 " Ulrich Hecht
2014-08-29 20:03 ` [PATCH 0/2] r8a777[89] dtsi sorting Geert Uytterhoeven
2014-09-01 1:24 ` Simon Horman
2014-09-01 1:34 ` Simon Horman [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=20140901013444.GI32075@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=ulrich.hecht+renesas@gmail.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).