SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/03] ARM: shmobile: r8a7779 Marzen legacy removal
Date: Fri, 17 Jul 2015 04:04:57 +0000	[thread overview]
Message-ID: <20150717040453.GA21932@verge.net.au> (raw)
In-Reply-To: <20150716075342.1198.63257.sendpatchset@little-apple>

On Thu, Jul 16, 2015 at 04:53:42PM +0900, Magnus Damm wrote:
> ARM: shmobile: r8a7779 Marzen legacy removal
> 
> [PATCH 01/03] ARM: shmobile: marzen: Remove legacy board code
> [PATCH 02/03] ARM: shmobile: r8a7779: Remove legacy SoC code
> [PATCH 03/03] ARM: shmobile: Remove marzen_defconfig
> 
> This series removes the r8a7779 Marzen legacy code. Board
> code for Marzen written in C and r8a7779 SoC code including
> old clock framework code and platform devices are removed.
> 
> Existing Marzen users need to move over to Multiplatform and
> shmobile_defconfig. The DT file r8a7779-marzen.dts file is
> the same as for the legacy case.
> 
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>

Thanks, I have queued these up.

FYI doing so was rather awkward as patch 01 and especially patch 02
have various conflicts with patches in several different branches.

For now I have gone with queuing them up on top of the marzen-reference
removal patches, which leaves minor conflicts mainly in Kconfig and
Makefiles. There is also a conflict with the marzen board code fix you
recently posted which is present in a separate fixes branch. I wonder if it
would make sense to drop that patch now removal of the code it fixes is
queued up.

  reply	other threads:[~2015-07-17  4:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  7:53 [PATCH 00/03] ARM: shmobile: r8a7779 Marzen legacy removal Magnus Damm
2015-07-17  4:04 ` Simon Horman [this message]
2015-07-17  6:32 ` Laurent Pinchart

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=20150717040453.GA21932@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