From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: r8a73a4: Remove legacy code
Date: Tue, 24 Feb 2015 15:23:29 +0000 [thread overview]
Message-ID: <1712555.MOqtjS5RND@avalon> (raw)
In-Reply-To: <1418771008-5676-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Simon,
On Tuesday 24 February 2015 08:44:18 Simon Horman wrote:
> On Thu, Feb 19, 2015 at 01:08:15PM -0500, Simon Horman wrote:
> > On Thu, Feb 19, 2015 at 01:02:09PM -0500, Simon Horman wrote:
> > > On Thu, Feb 19, 2015 at 06:48:03PM +0100, Geert Uytterhoeven wrote:
> > > > From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > > >
> > > > All r8a73a4 boards are now used with multiplatform kernels only. We
> > > > can remove all the unused r8a73a4 legacy device and clock registration
> > > > code.
> > > >
> > > > Signed-off-by: Laurent Pinchart
> > > > <laurent.pinchart+renesas@ideasonboard.com>
> > > > Acked-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > ---
> > > > Forgot to include this in the ape6evm multiplatform series.
> > >
> > > I think that I would rather hold off on this until ape6evm is
> > > working in renesas-devel.
> > >
> > > In particular I am referring to the mmc problem which you indicate
> > > has been fixed in next but not in mainline. It is the latter that
> > > renesas-devel is based on.
> >
> > It seems that v3.20-rc1 should have the required mmc changes. Assuming
> > the above statement is correct could you repost this patch once rc1 has
> > been released?
> >
> > As usual I plan to rebase the branches in renesas-devel on -rc1 once it
> > has been released. And to push the result into next. Due to travel and
> > other commitments this may not happen until a few days after -rc1 is
> > released.
>
> The mmc problems seem to be resolved in v4.0-rc1 and I have queued
> this patch up as part of rebasing renesas-devel/next on top of that rc
> release.
I can't find the patch in your next or devel branches. Am I looking at the
wrong tree ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-02-24 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 23:03 [PATCH] ARM: shmobile: r8a73a4: Remove legacy code Laurent Pinchart
2014-12-17 0:30 ` Simon Horman
2014-12-17 0:39 ` Laurent Pinchart
2015-02-19 17:48 ` Geert Uytterhoeven
2015-02-19 18:02 ` Simon Horman
2015-02-19 18:08 ` Simon Horman
2015-02-23 23:44 ` Simon Horman
2015-02-24 15:23 ` Laurent Pinchart [this message]
2015-02-24 15:30 ` Geert Uytterhoeven
2015-02-24 23:50 ` Simon Horman
2015-02-25 17:49 ` Sergei Shtylyov
2015-02-25 18:06 ` Geert Uytterhoeven
2015-02-25 23:23 ` Simon Horman
2015-02-25 23:28 ` Sergei Shtylyov
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=1712555.MOqtjS5RND@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 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.