linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] kconfig clean-up and mach-virt removal for 3.15
Date: Mon, 3 Mar 2014 12:53:25 +0800	[thread overview]
Message-ID: <20140303045320.GA9706@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <201402281855.18941.arnd@arndb.de>

On Fri, Feb 28, 2014 at 06:55:18PM +0100, Arnd Bergmann wrote:
> On Friday 28 February 2014, Arnd Bergmann wrote:
> > On Thursday 20 February 2014, Rob Herring wrote:
> > -------------------------------------------
> > > - Remove common kconfig options required by multi-platform builds out
> > > of individual platforms as they are redundant.
> > > - Make SMP, CACHE_L2X0 and GPIO config options user visible on
> > > multi-platform builds as most platforms enable these options and all
> > > platforms can run with them enabled.
> > > - Make multi-platform v6 default to more optimal v6k rather than v6
> > > - Remove the last bit of mach-virt and convert it to just a kconfig
> > > option.
> > 
> > Merged into next/cleanup. Very much appreciated changes!
> 
> Shawn, a quick warning about this: the Kconfig changes apparently
> cause a few conflicts with your tree in linux-next.
> 
> If you want to avoid them, you can merge
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
> tags/kconfig-cleanup-for-3.15
> 
> into the conflicting branches. I have merged it into arm-soc and
> is a stable branch in next/cleanups.

Ok, will do.  Thanks for the heads-up.

Shawn

      reply	other threads:[~2014-03-03  4:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 23:30 [GIT PULL] kconfig clean-up and mach-virt removal for 3.15 Rob Herring
2014-02-28 16:22 ` Arnd Bergmann
2014-02-28 17:55   ` Arnd Bergmann
2014-03-03  4:53     ` Shawn Guo [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=20140303045320.GA9706@shlinux1.ap.freescale.net \
    --to=shawn.guo@linaro.org \
    --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).