SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 00/04] ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3
Date: Wed, 15 Jul 2015 00:25:01 +0000	[thread overview]
Message-ID: <20150715002501.GF30642@verge.net.au> (raw)
In-Reply-To: <20150713061450.25534.96315.sendpatchset@little-apple>

Hi Magnus,

On Mon, Jul 13, 2015 at 03:14:50PM +0900, Magnus Damm wrote:
> ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3
> 
> [PATCH v3 01/04] ARM: shmobile: r8a7779: Generic SMP ops
> [PATCH v3 02/04] ARM: shmobile: marzen-reference: Remove C board code
> [PATCH v3 03/04] ARM: shmobile: Remove Marzen from shmobile_defconfig
> [PATCH v3 04/04] ARM: shmobile: r8a7779: Cleanup header file
> 
> This series is simply resending the remaining r8a7779 multiplatform
> cleanup patches. The code has not changed since V2:
> 
> [PATCH v2 00/06] ARM: shmobile: r8a7779 IRQ update and Marzen cleanup V2
> 
> With these patches applied the r8a7779 SoC gets DT-only multiplatform
> support and old C board code for multiplatform gets removed.
> 
> The legacy r8a7779 Marzen code is not touched by this series, but
> with these patches applied basic r8a7779 multiplatform SoC support
> is done and only a few I/O devices are legacy-only.

Thanks, I have queued these up.

Please send a follow-up patch to address Geert's observation that
CONFIG_MACH_MARZEN should be removed from multi_v7_defconfig.

  reply	other threads:[~2015-07-15  0:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:14 [PATCH v3 00/04] ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3 Magnus Damm
2015-07-15  0:25 ` Simon Horman [this message]
2015-07-15  1:16 ` Simon Horman
2015-07-15  5:56 ` Magnus Damm
2015-07-15  6:43 ` Simon Horman
2015-07-15  7:41 ` Geert Uytterhoeven

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=20150715002501.GF30642@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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