From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: shmobile: bockw: MMCIF support on DT
Date: Wed, 09 Oct 2013 20:20:46 +0000 [thread overview]
Message-ID: <3307226.GCex3zdijj@avalon> (raw)
In-Reply-To: <878uy9259u.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san and Simon,
On Tuesday 08 October 2013 17:11:10 Kuninori Morimoto wrote:
> Hi Simon, Laurent
>
> > > Laurent, could you let me know if you have a branch available with "ARM:
> > > shmobile: r8a7778: Fix pin control device address in DT". If not I'm
> > > happy
> > > to wait.
> >
> > I don't have one. The bug got introduced in v3.12-rc1, without any serious
> > consequence as the DT node wasn't used. The fix might even break the
> > bockw-
> > reference board if Morimoto-san's patch 4 isn't applied, as the PFC device
> > seems to be registered twice then (I haven't tested this).
> >
> > Morimoto-san, could you please test my fix on bockw-reference without your
> > patch series ? If it doesn't break anything then we could push it to
> > v3.12.
> > Otherwise we can include it with this series. Simon, would that be fine
> > with you ?
>
> I tested Laurent's fixup patch on
>
> - latest linus/master + fixup patch
> - renesas-devel-20131008 + fixup patch
>
> both works well
Thank you for testing this.
Simon, would you like to pick up the patch for v3.12 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-10-09 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 1:28 [PATCH 0/7] ARM: shmobile: bockw: MMCIF support on DT Kuninori Morimoto
2013-10-04 1:30 ` Kuninori Morimoto
2013-10-04 1:35 ` Kuninori Morimoto
2013-10-08 1:11 ` Simon Horman
2013-10-08 1:32 ` Kuninori Morimoto
2013-10-08 2:07 ` Simon Horman
2013-10-08 2:57 ` Kuninori Morimoto
2013-10-08 4:00 ` Simon Horman
2013-10-08 20:59 ` Laurent Pinchart
2013-10-09 0:11 ` Kuninori Morimoto
2013-10-09 20:20 ` Laurent Pinchart [this message]
2013-10-10 11:33 ` 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=3307226.GCex3zdijj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).