From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH V2 0/5] pinctrl: sh-pfc: pfc-r8a7790: Update VIN groups
Date: Tue, 10 Dec 2013 19:42:54 +0000 [thread overview]
Message-ID: <1780188.hNGucXYrGQ@avalon> (raw)
In-Reply-To: <1386699626-15803-1-git-send-email-valentine.barshak@cogentembedded.com>
Hi Valentine,
The patches are much easier to review split this way. Thank you for the great
work.
On Tuesday 10 December 2013 22:20:21 Valentine Barshak wrote:
> This adds missing VIN pins to the pfc-r8a7790 driver, and reorganizes
> the VIN groups to cover all possible configurations of VIN data pins.
> This also groups hsync and vsync pins together and renames "field_signal"
> and "data_enable" groups to "field" and "clkenb" respectively.
>
> Changes in version 2:
> * Split big patches into smaller series.
> * Reorganized the existing pin groups before adding new ones.
>
> Valentine Barshak (5):
> pinctrl: sh-pfc: pfc-r8a7790: Rename VIN pin groups
> pinctrl: sh-pfc: pfc-r8a7790: Group VIN0 HSYNC and VSYNC together
> pinctrl: sh-pfc: pfc-r8a7790: Reorganize VIN0 data pins
> pinctrl: sh-pfc: pfc-r8a7790: Add missing VIN1 pins
> pinctrl: sh-pfc: pfc-r8a7790: Add VIN2 and VIN3 pins
For the whole series,
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
I've applied the patches to my tree and will send a pull request for v3.14.
> drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 441 +++++++++++++++++++++++++++-----
> 1 file changed, 382 insertions(+), 59 deletions(-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-12-10 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 18:20 [PATCH V2 0/5] pinctrl: sh-pfc: pfc-r8a7790: Update VIN groups Valentine Barshak
2013-12-10 19:42 ` Laurent Pinchart [this message]
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=1780188.hNGucXYrGQ@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).