SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/2] pinctrl: sh-pfc: fix a typo and simplify a definition on sh73a0
Date: Wed, 13 Feb 2013 17:48:24 +0000	[thread overview]
Message-ID: <12720034.YvjkTUZKTP@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1302121633000.7059@axis700.grange>

Hi Simon,

On Wednesday 13 February 2013 17:53:34 Simon Horman wrote:
> On Wed, Feb 13, 2013 at 08:02:56AM +0100, Guennadi Liakhovetski wrote:
> > On Wed, 13 Feb 2013, Guennadi Liakhovetski wrote:
> > > On Wed, 13 Feb 2013, Simon Horman wrote:
> > > > On Tue, Feb 12, 2013 at 04:34:31PM +0100, Guennadi Liakhovetski wrote:
> > > > > Fix definition of the SDHIWP0 function and simplify the CPU_ALL_PORT
> > > > > definition on sh73a0.
> > > > > 
> > > > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > > > 
> > > > This patch appears to be against code that has been merged into
> > > > arm-soc for 3.9.
> > > > 
> > > > In particular the following change in the pfc branch of the renesas
> > > > tree a.k.a the arm-soc/renesas/pinmux branch of the arm-soc tree.
> > > > 
> > > > commit 5d5166dc39bcbe2c21d4fca034540133c415dce6
> > > > Author: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > > > Date:   Sat Dec 15 23:51:24 2012 +0100
> > > > 
> > > >     sh-pfc: Add sh73a0 pinmux support
> > > >     
> > > >     Signed-off-by: Laurent Pinchart
> > > >     <laurent.pinchart+renesas@ideasonboard.com>
> > > >     Acked-by: Paul Mundt <lethal@linux-sh.org>
> > > >     Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > > >     Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > > > 
> > > > As such, I would like to handle it separately from the other two
> > > > patches in this series which are against un-merged code.
> > > > 
> > > > Before I do so I would like to:
> > > > 
> > > > * Know about the severity of this problem.
> > > > 
> > > >   Does it break things?
> > > 
> > > Yes, .dts doesn't compile without the semicolon.
> > 
> > Ok, sorry, obviously, I was thinking about a different patch. Please,
> > ignore this.
> > 
> > As for breakage - so far I'm personally unaware of any breakage, which is
> > of course not to say, that none is possible.
> 
> Thanks. In any case it is probably appropriate for v3.10.
> In any case I'll wait to see what Laurent and Linus have to say.

Patches 1/2 should be squashed into the merge that introduced the issue (I 
think that's what you've done already) and 2/2 should be carried along with 
your other kzm9g-reference pinctrl patches for now.

I've taken patch 3/2 in my tree. Given the the SDHIWP0_PU function GPIO isn't 
used in mainline I don't think there's a need to fast-track it to v3.9, I will 
include it in my next pinctrl series for v3.10.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2013-02-13 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 15:34 [PATCH 3/2] pinctrl: sh-pfc: fix a typo and simplify a definition on sh73a0 Guennadi Liakhovetski
2013-02-13  1:28 ` Simon Horman
2013-02-13  6:59 ` Guennadi Liakhovetski
2013-02-13  7:02 ` Guennadi Liakhovetski
2013-02-13  8:53 ` Simon Horman
2013-02-13 17:48 ` Laurent Pinchart [this message]
2013-02-14  0:58 ` 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=12720034.YvjkTUZKTP@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