linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: device tree changes for 3.15, take 1
Date: Thu, 6 Feb 2014 14:45:05 +0100	[thread overview]
Message-ID: <201402061445.06234.arnd@arndb.de> (raw)
In-Reply-To: <20140205122258.GA13821@S2101-09.ap.freescale.net>

On Wednesday 05 February 2014, Shawn Guo wrote:
> Hi arm-soc folks,
> 
> This is basically imx-dt-3.14 pull request that missed the 3.14 merge
> window with the pingrp removal series applied on top of.  It also
> includes a few additional board support I collected since imx-dt-3.14.
> There will be another round of IMX DT changes for 3.15 later, but this
> one should be the majority.  Please pull, thanks.

Hi Shawn,

no objections to the stuff you add here, but the way it's organized
is not good. Instead of adding the controversial patches first and
then reverting them, please redo the series so you don't actually
have the patches in the history. I see that you have rebased the
patches on 3.14-rc1 already so there really shouldn't be any cross-
tree dependencies that make it necessary to keep them in.

Also, because of the pure size of the pull request:

 105 files changed, 14073 insertions(+), 3127 deletions(-)

it would be nice to split it up into smaller units. A good
separation would be to have new board support in one pull
request and the changes to existing boards in another one.

	Arnd

  reply	other threads:[~2014-02-06 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 12:23 [GIT PULL] ARM: imx: device tree changes for 3.15, take 1 Shawn Guo
2014-02-06 13:45 ` Arnd Bergmann [this message]
2014-02-06 15:01   ` Shawn Guo
2014-02-09 12:16   ` Shawn Guo
2014-02-10 15:19     ` Arnd Bergmann
2014-02-07 10:04 ` Heiko Stübner
2014-02-10  6:33   ` Shawn Guo

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=201402061445.06234.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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).