All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: genmai: remove defconfig
Date: Tue, 15 Jul 2014 11:58:21 +0000	[thread overview]
Message-ID: <3624228.NbiLenVez0@avalon> (raw)
In-Reply-To: <1405409364-23378-1-git-send-email-horms+renesas@verge.net.au>

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 ?

> ---
>  arch/arm/configs/genmai_defconfig | 122 -----------------------------------
> 1 file changed, 122 deletions(-)
>  delete mode 100644 arch/arm/configs/genmai_defconfig

-- 
Regards,

Laurent Pinchart


WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: genmai: remove defconfig
Date: Tue, 15 Jul 2014 13:58:21 +0200	[thread overview]
Message-ID: <3624228.NbiLenVez0@avalon> (raw)
In-Reply-To: <1405409364-23378-1-git-send-email-horms+renesas@verge.net.au>

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 ?

> ---
>  arch/arm/configs/genmai_defconfig | 122 -----------------------------------
> 1 file changed, 122 deletions(-)
>  delete mode 100644 arch/arm/configs/genmai_defconfig

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2014-07-15 11:58 UTC|newest]

Thread overview: 16+ 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:29 ` Simon Horman
2014-07-15  7:54 ` Wolfram Sang
2014-07-15  7:54   ` Wolfram Sang
2014-07-15 11:58 ` Laurent Pinchart [this message]
2014-07-15 11:58   ` Laurent Pinchart
2014-07-15 12:23   ` Simon Horman
2014-07-15 12:23     ` Simon Horman
2014-07-15 13:04     ` Simon Horman
2014-07-15 13:04       ` Simon Horman
2014-07-15 23:01       ` Laurent Pinchart
2014-07-15 23:01         ` Laurent Pinchart
2014-07-16  0:18         ` Simon Horman
2014-07-16  0:18           ` Simon Horman
2014-07-15 12:25 ` 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=3624228.NbiLenVez0@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.