From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
To: linux-sh@vger.kernel.org
Cc: horms@verge.net.au, devicetree@vger.kernel.org,
magnus.damm@gmail.com,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Subject: [PATCH 0/2] r8a777[89] dtsi sorting
Date: Fri, 29 Aug 2014 20:16:39 +0200 [thread overview]
Message-ID: <1409336201-708-1-git-send-email-ulrich.hecht+renesas@gmail.com> (raw)
Hi!
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).
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.
I'd also like to know if there is consensus on different/additional
standards that I'm not aware of.
CU
Uli
Ulrich Hecht (2):
ARM: shmobile: r8a7778 dtsi: sort it
ARM: shmobile: r8a7779 dtsi: sort it
arch/arm/boot/dts/r8a7778.dtsi | 56 ++---
arch/arm/boot/dts/r8a7779.dtsi | 472 ++++++++++++++++++++---------------------
2 files changed, 264 insertions(+), 264 deletions(-)
--
1.8.4.5
next reply other threads:[~2014-08-29 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:16 Ulrich Hecht [this message]
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
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=1409336201-708-1-git-send-email-ulrich.hecht+renesas@gmail.com \
--to=ulrich.hecht+renesas@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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).