All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: shmobile: fix kzm9g-reference compile breakage
Date: Thu, 14 Feb 2013 00:59:08 +0000	[thread overview]
Message-ID: <20130214005908.GH15879@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.1302121535330.7059@axis700.grange>

On Wed, Feb 13, 2013 at 05:16:36PM +0100, Laurent Pinchart wrote:
> Hi Simon,
> 
> On Wednesday 13 February 2013 11:31:19 Simon Horman wrote:
> > On Tue, Feb 12, 2013 at 03:55:55PM +0100, Guennadi Liakhovetski wrote:
> > > Recently many pin function names have been removed, as their users have
> > > been switched to use pinctrl. However, kzm9g-reference has been left
> > > unchanged, which broke its compilation. Fix this by switching over to
> > > pinctrl.
> > 
> > Thanks.
> > 
> > I'm rather unsure what to do about this.
> > 
> > On the one hand I would rather if the basic kzm9g-reference code didn't
> > depend on any more pinmux changes to allow it to flow upstream sooner than
> > later.
> > 
> > On the other hand things are clearly broken without some modifications to
> > the kzm9g-reference code to accomodate the pinmux changes.
> 
> Given that only two small patches are needed to fix the issue, I believe we 
> could sort this out in a "first come, first served" way. If the kzm9g-
> reference branch gets ready for mainline before my remaining pinctrl changes, 
> you can push it as-is, and I'll take the two patches listed below in my tree. 
> If the timeline is shifted the other way around, you will just need to take 
> the two patches in your tree.
> 
> Would that work for you ?

Yes, I think so.

      parent reply	other threads:[~2013-02-14  0:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 14:55 [PATCH 2/2] ARM: shmobile: fix kzm9g-reference compile breakage Guennadi Liakhovetski
2013-02-13  2:31 ` Simon Horman
2013-02-13 16:16 ` Laurent Pinchart
2013-02-14  0:59 ` Simon Horman [this message]

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=20130214005908.GH15879@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 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.