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: Mon, 10 Feb 2014 16:19:21 +0100 [thread overview]
Message-ID: <201402101619.22124.arnd@arndb.de> (raw)
In-Reply-To: <20140209121640.GA14588@S2101-09.ap.freescale.net>
On Sunday 09 February 2014, Shawn Guo wrote:
> On Thu, Feb 06, 2014 at 02:45:05PM +0100, Arnd Bergmann wrote:
> > On Wednesday 05 February 2014, Shawn Guo wrote:
> > 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.
>
> Okay. I just spent the weekend to rebuild the branch and reworked quite
> a lot of patches to wipe the pingrp stuff from the history.
Thanks!
> > 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.
>
> Some new board support are built on top of the updates to the existing
> files for purpose like sharing common part. And some updates are added
> on top of new board support along time goes. So it's hard to make such
> separation. Considering the amount of imx6 changes these days, I chose
> to split the branch into two, one for imx6 changes and the other for all
> the rest. Such separation does not involve too much interdependency.
Ok, good idea.
Arnd
next prev parent reply other threads:[~2014-02-10 15:19 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
2014-02-06 15:01 ` Shawn Guo
2014-02-09 12:16 ` Shawn Guo
2014-02-10 15:19 ` Arnd Bergmann [this message]
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=201402101619.22124.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.