From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 0/3] pinctrl: sh-pfc: Correct pin range comments
Date: Thu, 04 Feb 2016 20:53:23 +0200 [thread overview]
Message-ID: <1489274.AOuTy6zPSb@avalon> (raw)
In-Reply-To: <1448891996-5263-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
Thank you for the patches.
On Monday 30 November 2015 14:59:53 Geert Uytterhoeven wrote:
> Hi Laurent, Linus,
>
> This patch series corrects a few pin range comments in the Renesas
> pinctrl data. No functional changes.
>
> Thanks!
For the whole series,
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Geert Uytterhoeven (3):
> pinctrl: sh-pfc: emev2: Correct comment for CFI data pins
> pinctrl: sh-pfc: r8a7740: Correct comment for LCD1 data pins
> pinctrl: sh-pfc: sh73a0: Correct comment for LCD2 data pins
>
> drivers/pinctrl/sh-pfc/pfc-emev2.c | 2 +-
> drivers/pinctrl/sh-pfc/pfc-r8a7740.c | 2 +-
> drivers/pinctrl/sh-pfc/pfc-sh73a0.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-02-04 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 13:59 [PATCH 0/3] pinctrl: sh-pfc: Correct pin range comments Geert Uytterhoeven
2015-11-30 13:59 ` [PATCH 1/3] pinctrl: sh-pfc: emev2: Correct comment for CFI data pins Geert Uytterhoeven
2015-11-30 13:59 ` [PATCH 2/3] pinctrl: sh-pfc: r8a7740: Correct comment for LCD1 " Geert Uytterhoeven
2015-11-30 13:59 ` [PATCH 3/3] pinctrl: sh-pfc: sh73a0: Correct comment for LCD2 " Geert Uytterhoeven
2016-02-04 18:53 ` Laurent Pinchart [this message]
2016-02-08 15:36 ` [PATCH 0/3] pinctrl: sh-pfc: Correct pin range comments Geert Uytterhoeven
2016-02-15 19:42 ` Linus Walleij
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=1489274.AOuTy6zPSb@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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).