public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] RealView boardfile endgame
Date: Thu, 25 Feb 2016 17:10:42 +0100	[thread overview]
Message-ID: <3638303.456FExenOa@wuerfel> (raw)
In-Reply-To: <CACRpkdZ_oyJNTzC6Ji+19aRy3Ex47u2Khqd7_RwuGdK+TLTy_A@mail.gmail.com>

On Thursday 25 February 2016 16:29:31 Linus Walleij wrote:
> On Thu, Feb 25, 2016 at 3:29 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 25 February 2016 14:15:07 Linus Walleij wrote:
> >> This patch set deletes the RealView board files and moves it
> >> over to a pure Device Tree boot, deleting ~3500 LoC.
> (...)
> > This leaves the question whether we should do all the preparation
> > in 4.6 and then only take these for 4.7, or do them all at
> > once. I can see good reasons either way, but none of them
> > particularly strong. What did you have in mind here?
> 
> If the dependencies in CLCD and MTD make it in we'll just
> merge the whole thing IMO.
> 
> If these drag out, we merge the device trees and wait with
> removing the board files until v4.7.
> 
> I will still have some remaining cleanup for Integrator, Versatile
> and also Versatile Express however, but that is for later.
> 
> 

Ok, sounds good.

	Arnd

      reply	other threads:[~2016-02-25 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 13:15 [PATCH 0/4] RealView boardfile endgame Linus Walleij
2016-02-25 13:15 ` [PATCH 2/4] ARM: realview: reduce the RealView Kconfig Linus Walleij
2016-02-25 13:15 ` [PATCH 3/4] ARM: realview: imply Device Tree config Linus Walleij
2016-02-25 14:23   ` Arnd Bergmann
2016-02-25 14:58     ` Linus Walleij
2016-02-25 13:15 ` [PATCH 4/4] ARM: realview: cut board options from defconfig Linus Walleij
2016-02-25 14:29 ` [PATCH 0/4] RealView boardfile endgame Arnd Bergmann
2016-02-25 15:29   ` Linus Walleij
2016-02-25 16:10     ` Arnd Bergmann [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=3638303.456FExenOa@wuerfel \
    --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