linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.12
Date: Sun, 18 Aug 2013 03:57:03 +0000	[thread overview]
Message-ID: <20130818035703.GC30709@verge.net.au> (raw)
In-Reply-To: <20130814080405.GF30577@quad.lixom.net>

On Wed, Aug 14, 2013 at 01:04:05AM -0700, Olof Johansson wrote:
> On Wed, Aug 07, 2013 at 01:23:55PM +0900, Simon Horman wrote:
> > Hi Olof, Hi Arnd,
> > 
> > please consider these Renesas ARM based SoC defconfig updates for v3.12.
> > 
> > 
> > In relation to adding a new defconfig I would like to note that Magnus and
> > I are aware of your ongoing requests to reduce the number of shmobile
> > defconfigs and that we are making progress on that front in two ways:
> > 
> > * Two boards, and their defconfigs were scheduled for removal in v3.11
> >   and a further two boards and their defconfigs are scheduled for removal
> >   in v3.12.
> > 
> >   For reference the boards are: ap5evb, bonito, ag5evm and kota2
> > 
> > * More importantly, we are making significant progress towards being
> >   able to use multiplatform and thus consolidate most if not all
> >   of the shmobile defconfigs into either a single shmobile defconfig
> >   or a more generic ARM defconfig.
> > 
> >   The removal of the boards mentioned above helps this process
> >   by removing the need to update as much code. In particular code
> >   which we have limited or no access to hardware to test.
> > 
> >   The main remaining barrier here is common clocks which I current
> >   expect to take a few more release cycles to get in order.
> > 
> > 
> > The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:
> > 
> >   Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-defconfig-for-v3.12
> 
> Pulled. Looking forward to the removals. :)

Likewise.

  reply	other threads:[~2013-08-18  3:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  4:23 [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.12 Simon Horman
2013-08-07  4:24 ` [GIT PULL 1/4] ARM: shmobile: marzen: Enable ARM_APPENDED_DTB in defconfig Simon Horman
2013-08-07  4:24 ` [GIT PULL 2/4] ARM: shmobile: Add lager defconfig Simon Horman
2013-08-07  4:24 ` [GIT PULL 3/4] ARM: shmobile: ape6evm: Enable gpio-keys in defconfig Simon Horman
2013-08-07  4:24 ` [GIT PULL 4/4] ARM: shmobile: ape6evm: Enable gpio-leds " Simon Horman
2013-08-14  8:04 ` [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.12 Olof Johansson
2013-08-18  3:57   ` Simon Horman [this message]
2013-10-01  2:38 ` [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.13 Simon Horman
2013-10-01  2:38   ` [PATCH 1/4] ARM: shmobile: marzen: Select DRM_RCAR_DU in defconfig Simon Horman
2013-10-01  2:38   ` [PATCH 2/4] ARM: shmobile: lager: " Simon Horman
2013-10-01  2:38   ` [PATCH 3/4] ARM: shmobile: bockw defconfig: add Sound support Simon Horman
2013-10-01  2:38   ` [PATCH 4/4] ARM: shmobile: Add koelsch defconfig Simon Horman
2013-10-07 18:38   ` [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.13 Olof Johansson

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=20130818035703.GC30709@verge.net.au \
    --to=horms@verge.net.au \
    --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).