From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 00/29] SH pinctrl and pinmux implementation
Date: Thu, 14 Mar 2013 09:12:23 +0000 [thread overview]
Message-ID: <20130314091223.GJ11196@verge.net.au> (raw)
In-Reply-To: <1362740170-19073-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Wed, Mar 13, 2013 at 06:27:14PM +0100, Linus Walleij wrote:
> On Wed, Mar 13, 2013 at 11:24 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Mar 13, 2013 at 06:07:46AM +0100, Linus Walleij wrote:
> >> On Sat, Mar 9, 2013 at 5:28 AM, Simon Horman <horms@verge.net.au> wrote:
> >>
> >> > 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.
> >>
> >> Hm you shouldn't be basing anything on for-next in the pinctrl tree because
> >> that is rebased all the time. If you need to base off the pinctrl tree, use
> >> the "devel" branch, after handshake with me.
> >
> > Sure, I can rebase on the devel branch.
> > Can you give me an "ok" to do that and by implication push a
> > branch based on devel through arm-soc?
>
> Yes the top of that branch should be OK, I hope we do not
> screw anything up, then we will notice :-)
Thanks!
prev parent reply other threads:[~2013-03-14 9:12 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
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 [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=20130314091223.GJ11196@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox