All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 00/29] SH pinctrl and pinmux implementation
Date: Mon, 11 Mar 2013 20:14:53 +0000	[thread overview]
Message-ID: <1414889.WPzFUJXkjh@avalon> (raw)
In-Reply-To: <1362740170-19073-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Simon,

On Saturday 09 March 2013 05:28:27 Simon Horman wrote:
> On Fri, Mar 08, 2013 at 04:43:11PM +0100, Laurent Pinchart wrote:
> > On Friday 08 March 2013 16:25:53 Simon Horman wrote:
> > > On Fri, Mar 08, 2013 at 11:55:41AM +0100, Laurent Pinchart wrote:
> > > > Hello,
> > > > 
> > > > Here's the fourth version of the SuperH and SH Mobile pin controllers
> > > > (PFC) pinctrl and pinmux support patches. The patches are available
> > > > from my git tree at
> > > > 
> > > >         git://linuxtv.org/pinchartl/fbdev.git pinmux/3.9/pinctrl
> > > > 
> > > > The patches are based on top of the following two commits from Linus'
> > > > pinctrl tree:
> > > > 
> > > > 022ab148d28e8 "pinctrl: Declare operation structures as const"
> > > > a72149e82b65b "pinctrl: core: use devres_release() instead of
> > > > devres_destroy()"
> > > 
> > > I assume that I should make a branch based on a branch which includes
> > > those commits.
> > > 
> > > Linus, is there a stable branch that includes those commits at this
> > > time?
> > 
> > 022ab148d28e8 is in Linus' for-next branch, so I think it should be
> > stable.
> > 
> > > > merged into the pinmux/3.9/base branch in my tree, as well as the
> > > > "ARM: shmobile: marzen: Include mmc/host.h" patch hand-picked from the
> > > > mailing list to fix a compilation breakage.
> > > 
> > > Thanks, I'll send that as a fix inclusion in 3.9.
> > 
> > Could you create a branch based on v3.9-rc1 + the mmc fix + anything you
> > deem appropriate and merge 022ab148d28e8 from
> > git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
> > into it ? I'll then rebase my patches on top of that (I won't repost them
> > as that shouldn't make any difference in the patches themselves).
> 
> Sure.
> 
> I have made a merge of the fixes branch with Linus's for-next branch
> and pushed the result as a new pinmux-base branch.

Thank you. I've rebased my tree on top of that. You can pull the 
pinmux/3.9/pfc-funcs branch (based on top of pinmux/3.9/pinctrl, so you will 
get this patch set as well as "[PATCH v3 00/64] PFC pinctrl functions for 
sh7372, sh73a0, r8a7740 and r8a7779") directly.

> I am still a little undecided about what to do about handling
> pinmux changes for kzm9g-reference. But I think the best option
> may be to base them on top of pinmux-base.

Or on top of my patches ?

> I agree there is no need to repost your patches at this stage.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2013-03-11 20:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 10:55 [PATCH v4 00/29] SH pinctrl and pinmux implementation Laurent Pinchart
2013-03-08 15:25 ` Simon Horman
2013-03-08 15:43 ` Laurent Pinchart
2013-03-09  4:28 ` Simon Horman
2013-03-11 20:14 ` Laurent Pinchart [this message]
2013-03-13  5:07 ` Linus Walleij
2013-03-13 10:24 ` Simon Horman
2013-03-13 17:27 ` Linus Walleij
2013-03-14  9:12 ` 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=1414889.WPzFUJXkjh@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.