public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: horms@verge•net.au (Simon Horman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] Renesas ARM-based SoC defconfig for v3.8
Date: Thu, 1 Nov 2012 08:46:48 +0800	[thread overview]
Message-ID: <20121101004647.GA3598@verge.net.au> (raw)
In-Reply-To: <201210302141.27919.arnd@arndb.de>

On Tue, Oct 30, 2012 at 09:41:27PM +0000, Arnd Bergmann wrote:
> On Tuesday 30 October 2012, Simon Horman wrote:
> > While I am more than happy to help address the issues raised in this
> > thread, and others that arise. There do seem to be a number of issues
> > between where we are now and a more generic shmobile_defconfig. I would
> > like consideration given to allowing the exixting, working, well-maintained,
> > per-board defconfigs to be updated until these issues have been resolved.
> 
> Yes, no problem. This seemed like a low-hanging fruit initially but has
> turned into something much bigger now.
> 
> Instead of attacking all these at ones, we can leave them as something
> worthwhile doing later. I noticed that out of the 11 shmobile defconfigs,
> only three (marzen, kzm9d and kzm9g) actually have a nonzero MEMORY_START.
> 
> Maybe it's possible to consolidate all or some of the others first, since
> they should still work with the same uImage at the expense of just making
> the early debugging a little harder, as we discussed earlier.
> 
> For all I know, these three boards are also the ones seeing the most
> ongoing development, so you could start by using a shared defconfig
> for the oldest (ARM11 based) boards at first that are also less likely
> to impact new development starting from the defconfig.

Thanks, good observations. I will look into that.

My expectation is that marzen and kzm9g will continue to see
heavy development in the near future.

      reply	other threads:[~2012-11-01  0:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  4:38 [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-10-17  4:38 ` [PATCH 1/2] ARM: shmobile: mackerel: defconfig update Simon Horman
2012-10-17  4:38 ` [PATCH 2/2] ARM: shmobile: armadillo800eva: enable L2X0 cache on defconfig Simon Horman
2012-10-17 13:42 ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Arnd Bergmann
2012-10-18  0:58   ` Simon Horman
2012-10-18  7:29     ` Arnd Bergmann
2012-10-18  8:13       ` Simon Horman
2012-10-19  3:09         ` Simon Horman
2012-10-19  8:18           ` Arnd Bergmann
2012-10-22  0:33             ` Simon Horman
2012-10-22  1:51               ` Simon Horman
2012-10-22 14:12                 ` Arnd Bergmann
2012-10-22 18:20                   ` Nicolas Pitre
2012-10-30  7:45                     ` Simon Horman
2012-10-30 21:41                       ` Arnd Bergmann
2012-11-01  0:46                         ` 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=20121101004647.GA3598@verge.net.au \
    --to=horms@verge$(echo .)net.au \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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