SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: genmai: remove defconfig
Date: Tue, 15 Jul 2014 13:04:59 +0000	[thread overview]
Message-ID: <20140715130458.GI25333@verge.net.au> (raw)
In-Reply-To: <20140715122350.GD25333@verge.net.au>

On Tue, Jul 15, 2014 at 09:23:50PM +0900, Simon Horman wrote:
> On Tue, Jul 15, 2014 at 01:58:21PM +0200, Laurent Pinchart wrote:
> > Hi Simon,
> > 
> > Thank you for the patch.
> > 
> > On Tuesday 15 July 2014 16:29:24 Simon Horman wrote:
> > > The genmai board code is scheduled for removal and once
> > > that occurs the defconfig will be of no use. Remove it.
> > > 
> > > Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > > Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > 
> > Acked-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > 
> > Now that the MTU2 boot issue has been solved (thank you for tracking it down), 
> > am I correct to assume that all timer patches, the genmai board file removal 
> > series and this patch will make it to v3.17 ?
> 
> Yes, that is my plan.
> 
> I hope to have them queued up this evening.

Please take a look at renesas-next-v3.16-rc3-20140715v2 and let
me know if anything is missing.

  reply	other threads:[~2014-07-15 13:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  7:29 [PATCH] ARM: shmobile: genmai: remove defconfig Simon Horman
2014-07-15  7:54 ` Wolfram Sang
2014-07-15 11:58 ` Laurent Pinchart
2014-07-15 12:23   ` Simon Horman
2014-07-15 13:04     ` Simon Horman [this message]
2014-07-15 23:01       ` Laurent Pinchart
2014-07-16  0:18         ` Simon Horman
2014-07-15 12:25 ` Simon Horman

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=20140715130458.GI25333@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