linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 0/9] sh-pfc: modify PINMUX_IPSR_MSEL() and r8a7795 support
Date: Thu, 03 Sep 2015 00:25:56 +0000	[thread overview]
Message-ID: <23650612.PHpdfx055U@avalon> (raw)
In-Reply-To: <87wpw9jn3i.wl%kuninori.morimoto.gx@renesas.com>

Hi Morimoto-san,

Thank you for the patches.

On Wednesday 02 September 2015 07:33:21 Kuninori Morimoto wrote:
> Hi LinusW, Laurent
> 
> These are new version of r8a7795 PFC support.
> This time it includes PINMUX_IPSR_MSEL() modify patch too.
> 
> r8a7795 needs 1) 8) 9)
> 2) - 7) are cleanup patches, but not related to r8a7795

For patches 1-7 and patch 9,

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> This time r8a7795 PFC driver is using many macros.
> I took precedence "readable code" more than "80 character".
> These macro are same as "datasheet" style. So, I believe review is easy.
> 
> Kuninori Morimoto (9):
>       1) sh-pfc: modify PINMUX_IPSR_MSEL() macro order
>       2) sh-pfc: pfc-sh7734: use PINMUX_IPSR_MSEL()
>       3) sh-pfc: pfc-r8a7794: use PINMUX_IPSR_MSEL()
>       4) sh-pfc: pfc-r8a7791: use PINMUX_IPSR_MSEL()
>       5) sh-pfc: pfc-r8a7790: use PINMUX_IPSR_MSEL()
>       6) sh-pfc: pfc-r8a7779: use PINMUX_IPSR_MSEL()
>       7) sh-pfc: remove unused PINMUX_IPSR_MODSEL_DATA()
>       8) sh-pfc: Initial R8A7795 PFC support
>       9) sh-pfc: r8a7795: add SCIFx support

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2015-09-03  0:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  7:33 [PATCH 0/9] sh-pfc: modify PINMUX_IPSR_MSEL() and r8a7795 support Kuninori Morimoto
2015-09-02  7:44 ` [PATCH 1/9] sh-pfc: modify PINMUX_IPSR_MSEL() macro order Kuninori Morimoto
2015-09-02  8:05   ` Simon Horman
2015-09-25 16:43   ` Linus Walleij
2015-09-02  7:46 ` [PATCH 2/9] sh-pfc: pfc-sh7734: use PINMUX_IPSR_MSEL() Kuninori Morimoto
2015-09-02  7:46 ` [PATCH 3/9] sh-pfc: pfc-r8a7794: " Kuninori Morimoto
2015-09-02  7:46 ` [PATCH 4/9] sh-pfc: pfc-r8a7791: " Kuninori Morimoto
2015-09-02  7:47 ` [PATCH 5/9] sh-pfc: pfc-r8a7790: " Kuninori Morimoto
2015-09-02  7:47 ` [PATCH 6/9] sh-pfc: pfc-r8a7779: " Kuninori Morimoto
2015-09-02  7:47 ` [PATCH 7/9] sh-pfc: remove unused PINMUX_IPSR_MODSEL_DATA() Kuninori Morimoto
2015-09-02  7:47 ` [PATCH 8/9] sh-pfc: Initial R8A7795 PFC support Kuninori Morimoto
2015-09-02 14:58   ` Geert Uytterhoeven
2015-09-03  0:11     ` Kuninori Morimoto
2015-09-02  7:48 ` [PATCH 9/9] sh-pfc: r8a7795: add SCIFx support Kuninori Morimoto
2015-09-02  9:29 ` [PATCH 0/9] sh-pfc: modify PINMUX_IPSR_MSEL() and r8a7795 support Geert Uytterhoeven
2015-09-03  0:25 ` 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=23650612.PHpdfx055U@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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).