From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: [GIT PULL FOR v3.13] SH PFC pin definitions for I2C and SRU/SSI
Date: Tue, 24 Sep 2013 10:34:03 +0000 [thread overview]
Message-ID: <1527335.Z2uP9kBimX@avalon> (raw)
Hi Linus,
Here are two patches that add pin definitions to the sh-pfc driver. If you
believe they can go to v3.12 please feel free to include them in your next
fixes pull request. Otherwise please pull them in your for-next branch.
The following changes since commit cfa8b3f54e00b2300a2562c00d4d0cac48379ddb:
Merge branch 'devel' into for-next (2013-09-23 11:26:59 +0200)
are available in the git repository at:
git://linuxtv.org/pinchartl/fbdev.git pinmux/next
for you to fetch changes up to 70702bfc13c4f96f2f05d4ce2eb110cd1735fef5:
sh-pfc: r8a7790: Add I2C pin groups and functions (2013-09-24 12:23:42
+0200)
----------------------------------------------------------------
Kuninori Morimoto (1):
sh-pfc: r8a7778: Add SRU/SSI pin support
Ulrich Hecht (1):
sh-pfc: r8a7790: Add I2C pin groups and functions
drivers/pinctrl/sh-pfc/pfc-r8a7778.c | 125 ++++++++++++++++++++++++++++++++++
drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 82 ++++++++++++++++++++++++++++
2 files changed, 207 insertions(+)
--
Regards,
Laurent Pinchart
reply other threads:[~2013-09-24 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1527335.Z2uP9kBimX@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).