From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 00/88] PFC pinctrl functions for sh7372, sh73a0, r8a7740 and r8a7779
Date: Fri, 15 Mar 2013 15:37:57 +0000 [thread overview]
Message-ID: <20130315153753.GA16561@verge.net.au> (raw)
In-Reply-To: <1363215633-4264-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Fri, Mar 15, 2013 at 01:35:47PM +0100, Laurent Pinchart wrote:
> Hi Simon,
>
> On Friday 15 March 2013 07:25:28 Simon Horman wrote:
> > On Thu, Mar 14, 2013 at 03:01:48PM +0100, Laurent Pinchart wrote:
> > > On Thursday 14 March 2013 14:55:00 Linus Walleij wrote:
> > > > On Thu, Mar 14, 2013 at 2:39 PM, Laurent Pinchart wrote:
> > > > > [Me]
> > > > >
> > > > >> I merged a patch like this only yesterday to my fixes branch.
> > > > >>
> > > > >> commit bf4d7be57ba9040347065f48a60f895a254f6e28
> > > > >> Author: Sachin Kamat <sachin.kamat@linaro.org>
> > > > >> Date: Wed Mar 13 17:13:46 2013 +0530
> > > > >> pinctrl: generic: Fix compilation error
> > > > >
> > > > > Great, thank you. Is that patch present in a stable branch that Simon
> > > > > could merge ?
> > > >
> > > > Yes the fixes branch in the pinctrl tree.
> > >
> > > Thank you. Simon, it looks like we'll need another rebase :-/ Could you
> > > please merge that branch into your tree and give me the name of the
> > > resulting branch on which I'll rebase the PFC patches ?
> >
> > Sure, I have merged Linus's fixes branch into pinmux-base in the renesas
> > tree and pushed it to kernel.org. It should be there in a few minutes.
> > For reference the head commit is:
> >
> > commit 47f4e0c1c87f34bf1fc74b8935a37d229a147946
> > Merge: a9324f6 bf4d7be
> > Author: Simon Horman <horms+renesas@verge.net.au>
> > Date: Fri Mar 15 07:16:28 2013 +0100
> >
> > Merge branch 'fixes' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl into
> > pinmux-base
>
> Thank you. I've rebased my branches on top of that and pushed the result to
>
> git://linuxtv.org/pinchartl/fbdev.git
Thanks, that seems better.
I have pushed the pinmux/3.9/functions of your fbdev tree
as the pinmux branch of my renesas tree on kernel.org.
I have also rebased and pushed my boards-base, boards and next branches
accordingly.
prev parent reply other threads:[~2013-03-15 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 22:59 [PATCH v4 00/88] PFC pinctrl functions for sh7372, sh73a0, r8a7740 and r8a7779 Laurent Pinchart
2013-03-14 9:20 ` Simon Horman
2013-03-14 9:46 ` Simon Horman
2013-03-14 12:54 ` Laurent Pinchart
2013-03-14 13:31 ` Linus Walleij
2013-03-14 13:39 ` Laurent Pinchart
2013-03-14 13:55 ` Linus Walleij
2013-03-14 14:01 ` Laurent Pinchart
2013-03-14 15:09 ` Linus Walleij
2013-03-14 15:13 ` Laurent Pinchart
2013-03-15 6:25 ` Simon Horman
2013-03-15 12:35 ` Laurent Pinchart
2013-03-15 15:37 ` 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=20130315153753.GA16561@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.