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: pinmux missing from next in renesas tree
Date: Thu, 28 Mar 2013 08:40:14 +0000	[thread overview]
Message-ID: <3891776.FUARFIdxEg@avalon> (raw)
In-Reply-To: <20130328003634.GF20736@verge.net.au>

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


  reply	other threads:[~2013-03-28  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  0:36 pinmux missing from next in renesas tree Simon Horman
2013-03-28  8:40 ` Laurent Pinchart [this message]
2013-03-28  9:09 ` 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=3891776.FUARFIdxEg@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.