From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/4] r8a7793 pin control support
Date: Tue, 12 May 2015 07:31:13 +0000 [thread overview]
Message-ID: <4634674.uqpogLZnTA@avalon> (raw)
In-Reply-To: <1431015037-25254-1-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Ulrich,
Thank you for the patches.
On Thursday 07 May 2015 18:10:33 Ulrich Hecht wrote:
> Hi!
>
> This is the PFC portion broken out of the previously posted r8a7793 series.
> Sharing the code of the r8a7791 implementation, it is now about 6000 lines
> smaller. *cough*
>
> The one feature that was missing in the existing r8a7791 PFC implementation
> is the SSP pin group, which has been moved to a separate patch in this
> series.
For patches 1 to 3,
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
For patch 4, I have the same comment as Geert.
> Ulrich Hecht (4):
> pinctrl: sh-pfc: Add r8a7793 support
> pinctrl: sh-pfc: Enable building of r8a7793 PFC support
> pinctrl: sh-pfc: Add renesas,pfc-r8a7793 to binding documentation
> pinctrl: sh-pfc: r8a7791/3: Add SSP pin group
>
> .../bindings/pinctrl/renesas,pfc-pinctrl.txt | 3 +-
> drivers/pinctrl/sh-pfc/Kconfig | 5 +++
> drivers/pinctrl/sh-pfc/Makefile | 1 +
> drivers/pinctrl/sh-pfc/core.c | 6 ++++
> drivers/pinctrl/sh-pfc/core.h | 1 +
> drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 41 +++++++++++++++++++
> 6 files changed, 56 insertions(+), 1 deletion(-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-05-12 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 16:10 [PATCH 0/4] r8a7793 pin control support Ulrich Hecht
2015-05-07 16:10 ` [PATCH 3/4] pinctrl: sh-pfc: Add renesas,pfc-r8a7793 to binding documentation Ulrich Hecht
2015-05-12 7:22 ` [PATCH 0/4] r8a7793 pin control support Linus Walleij
2015-05-12 7:31 ` Laurent Pinchart [this message]
2015-05-12 8:48 ` Ulrich Hecht
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=4634674.uqpogLZnTA@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