SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/7] ARM: shmobile: ape6evm: multiplatform support
Date: Thu, 18 Dec 2014 01:25:02 +0000	[thread overview]
Message-ID: <20141218012501.GA6142@verge.net.au> (raw)
In-Reply-To: <1418747163-21729-1-git-send-email-ulrich.hecht+renesas@gmail.com>

On Thu, Dec 18, 2014 at 10:22:00AM +0900, Magnus Damm wrote:
> Hi Simon,
> 
> On Thu, Dec 18, 2014 at 9:19 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Dec 17, 2014 at 05:20:15PM +0100, Ulrich Hecht wrote:
> >> On Wed, Dec 17, 2014 at 2:23 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> > Hi Ulrich and Simon,
> >> >
> >> > On Wed, Dec 17, 2014 at 1:25 AM, Ulrich Hecht
> >> > <ulrich.hecht+renesas@gmail.com> wrote:
> >> >> It is split in such a way that the first five patches can be merged without
> >> >> breaking either of the two legacy platforms.  Simon, please pick those up.
> >> >> (Or the first three, if adding a multiplatform target that does not build is
> >> >> a problem.) Thank you.
> >> >
> >> > The first patch seems to have some issue reported by Laurent. It needs
> >> > to be reworked.
> >> >
> >> > Patch 2-5 should be possible to merge as-is unless I'm mistaken.
> >> >
> >> > Simon, if you don't mind, can you please consider picking up 2-5 before 1, 6-7?
> >>
> >> I respun the series following Laurent's suggestions, there should be
> >> no need for special-casing anymore.
> >>
> >> > As for patch 6-7 and the sh73a4 legacy removal code by Laurent, I
> >> > think the main blocker there is the r8a73a4 CCF support patch. I don't
> >> > want to remove legacy code before reference is at least half-complete.
> >> >
> >> > How can we move forward on the r8a73a4 CCF bits?
> >>
> >> For starters I have sent a new version of the series with the last
> >> remaining trivialities fixed.
> >
> > Thanks, that seems clean to me. And I see that Laurent has Acked the
> > changes. I will queue those up.
> 
> Thanks. I assume you guys work out the CCF vs the shmobile ordering
> and keep at least one DT-reference implementation working at any given
> time.

Yes, that is the assumption that I am working on.

  parent reply	other threads:[~2014-12-18  1:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 16:25 [PATCH v2 0/7] ARM: shmobile: ape6evm: multiplatform support Ulrich Hecht
2014-12-17  1:23 ` Magnus Damm
2014-12-17  4:57 ` Simon Horman
2014-12-17 16:20 ` Ulrich Hecht
2014-12-18  0:19 ` Simon Horman
2014-12-18  1:22 ` Magnus Damm
2014-12-18  1:25 ` Simon Horman [this message]
2014-12-18  1:33 ` Magnus Damm

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=20141218012501.GA6142@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