* pinmux missing from next in renesas tree
@ 2013-03-28 0:36 Simon Horman
2013-03-28 8:40 ` Laurent Pinchart
2013-03-28 9:09 ` Simon Horman
0 siblings, 2 replies; 3+ messages in thread
From: Simon Horman @ 2013-03-28 0:36 UTC (permalink / raw)
To: linux-sh
Unfortunately I forgot to merge pinmux into the next branch
I pushed last night and tagged as renesas-next-20130327.
I have re-pushed and re-taged with pinmux merged.
And also pushed pinmux which was one patch behind my local version.
For reference the relevant commit ids are:
next, renesas-next-20130327: 3f9904f90ec7729c8ac0bc554fed67d4f9d5bd59
(Merge branch 'pinmux' into next)
pinmux: 5ae81435c987e2ef071452d438770865814e8390
(sh-pfc: r8a7779: Split DU input and output pixel clocks)
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: pinmux missing from next in renesas tree
2013-03-28 0:36 pinmux missing from next in renesas tree Simon Horman
@ 2013-03-28 8:40 ` Laurent Pinchart
2013-03-28 9:09 ` Simon Horman
1 sibling, 0 replies; 3+ messages in thread
From: Laurent Pinchart @ 2013-03-28 8:40 UTC (permalink / raw)
To: linux-sh
Hi Simon,
On Thursday 28 March 2013 09:36:34 Simon Horman wrote:
> Unfortunately I forgot to merge pinmux into the next branch
> I pushed last night and tagged as renesas-next-20130327.
>
> I have re-pushed and re-taged with pinmux merged.
> And also pushed pinmux which was one patch behind my local version.
>
> For reference the relevant commit ids are:
>
> next, renesas-next-20130327: 3f9904f90ec7729c8ac0bc554fed67d4f9d5bd59
> (Merge branch 'pinmux' into next)
> pinmux: 5ae81435c987e2ef071452d438770865814e8390
> (sh-pfc: r8a7779: Split DU input and output pixel clocks)
Thanks a lot.
I've rebased all my branches on top of renesas-next-20130328 and there's no
patch missing except for the "[PATCH 0/3] sh-pfc: r8a7779: Improve readability
with a new macro" series that will need a v2 anyway.
I've also successfully test that tag with the DU driver on the Marzen board.
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pinmux missing from next in renesas tree
2013-03-28 0:36 pinmux missing from next in renesas tree Simon Horman
2013-03-28 8:40 ` Laurent Pinchart
@ 2013-03-28 9:09 ` Simon Horman
1 sibling, 0 replies; 3+ messages in thread
From: Simon Horman @ 2013-03-28 9:09 UTC (permalink / raw)
To: linux-sh
On Thu, Mar 28, 2013 at 09:40:14AM +0100, Laurent Pinchart wrote:
> Hi Simon,
>
> On Thursday 28 March 2013 09:36:34 Simon Horman wrote:
> > Unfortunately I forgot to merge pinmux into the next branch
> > I pushed last night and tagged as renesas-next-20130327.
> >
> > I have re-pushed and re-taged with pinmux merged.
> > And also pushed pinmux which was one patch behind my local version.
> >
> > For reference the relevant commit ids are:
> >
> > next, renesas-next-20130327: 3f9904f90ec7729c8ac0bc554fed67d4f9d5bd59
> > (Merge branch 'pinmux' into next)
> > pinmux: 5ae81435c987e2ef071452d438770865814e8390
> > (sh-pfc: r8a7779: Split DU input and output pixel clocks)
>
> Thanks a lot.
>
> I've rebased all my branches on top of renesas-next-20130328 and there's no
> patch missing except for the "[PATCH 0/3] sh-pfc: r8a7779: Improve readability
> with a new macro" series that will need a v2 anyway.
>
> I've also successfully test that tag with the DU driver on the Marzen board.
Great, thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-03-28 9:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-28 0:36 pinmux missing from next in renesas tree Simon Horman
2013-03-28 8:40 ` Laurent Pinchart
2013-03-28 9:09 ` Simon Horman
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.