From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: pinmux missing from next in renesas tree
Date: Thu, 28 Mar 2013 00:36:34 +0000 [thread overview]
Message-ID: <20130328003634.GF20736@verge.net.au> (raw)
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)
next reply other threads:[~2013-03-28 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 0:36 Simon Horman [this message]
2013-03-28 8:40 ` pinmux missing from next in renesas tree Laurent Pinchart
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=20130328003634.GF20736@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