linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Third Round of Renesas ARM Based SoC DT Updates for v3.15
Date: Mon, 17 Mar 2014 16:35:46 +0900	[thread overview]
Message-ID: <20140317073546.GA28083@verge.net.au> (raw)
In-Reply-To: <20140317071840.GD21917@quad.lixom.net>

On Mon, Mar 17, 2014 at 12:22:45AM -0700, Olof Johansson wrote:
> On Fri, Feb 21, 2014 at 03:12:51PM +0900, Simon Horman wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> > 
> > Please consider this third round of Renesas ARM based SoC DT updates for v3.15.
> > 
> > This pull request is based on the previous round of
> > such requests, tagged as renesas-dt2-for-v3.15,
> > which I have already sent a pull-request for.
> > 
> > 
> > The following changes since commit e02ee513eed4bb780848a5cedbd4b39afb395d3e:
> > 
> >   ARM: shmobile: koelsch dts: Add QSPI nodes (2014-02-06 20:36:12 +0900)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt3-for-v3.15
> 
> Merged.
> 
> For new DT contents, please pick a sort order. Most platforms use the actual
> unit address as the ordering, and not alphabetical based on node name. If you
> sort, new additions are less likely to conflict since they won't just be
> appended.
> 
> If you pick an order, you'll maybe have to re-sort some of your DTS files. Do
> so at the beginning of a release cycle and use that as a base for any new
> changes when you do.

Thanks. I believe we have been aiming, though not at all consistently,
for alphabetical order. I'll see about getting things cleaned up
for the beginning of the next cycle.

      reply	other threads:[~2014-03-17  7:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  6:12 [GIT PULL] Third Round of Renesas ARM Based SoC DT Updates for v3.15 Simon Horman
2014-02-21  6:12 ` [PATCH 01/13] ARM: shmobile: r8a7790 dtsi: Add QSPI node Simon Horman
2014-02-21  6:12 ` [PATCH 02/13] ARM: shmobile: lager dts: Add QSPI nodes Simon Horman
2014-02-21  6:12 ` [PATCH 03/13] ARM: shmobile: lager: add SDHI0/2 support on DTS Simon Horman
2014-02-21  6:12 ` [PATCH 04/13] ARM: shmobile: r8a7778 dtsi: Remove duplicate i2c nodes Simon Horman
2014-02-21  6:12 ` [PATCH 05/13] ARM: shmobile: lager: Add DU device to DTS Simon Horman
2014-02-21  6:12 ` [PATCH 06/13] ARM: shmobile: koelsch-reference: " Simon Horman
2014-02-21  6:12 ` [PATCH 07/13] ARM: shmobile: r8a7791: remove superfluous interrupt-parents Simon Horman
2014-02-21  6:12 ` [PATCH 08/13] ARM: shmobile: r8a7790: " Simon Horman
2014-02-21  6:12 ` [PATCH 09/13] ARM: shmobile: r8a7790: add i2c aliases to dtsi Simon Horman
2014-02-21  6:12 ` [PATCH 10/13] ARM: shmobile: r8a7791: add i2c master nodes " Simon Horman
2014-02-21  6:12 ` [PATCH 11/13] ARM: shmobile: r8a7791: add i2c2 bus to koelsch dt Simon Horman
2014-02-21  6:12 ` [PATCH 12/13] ARM: shmobile: r7s72100: add nodes for i2c controllers to dtsi Simon Horman
2014-02-21  6:12 ` [PATCH 13/13] ARM: shmobile: genmai: adapt dts to use native i2c driver Simon Horman
2014-03-17  7:22 ` [GIT PULL] Third Round of Renesas ARM Based SoC DT Updates for v3.15 Olof Johansson
2014-03-17  7:35   ` 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=20140317073546.GA28083@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).