From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 3/3] pinctrl: sh-pfc: sh73a0: Correct comment for LCD2 data pins
Date: Mon, 30 Nov 2015 14:59:56 +0100 [thread overview]
Message-ID: <1448891996-5263-4-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1448891996-5263-1-git-send-email-geert+renesas@glider.be>
The 12 data pins of LCD2 are numbered 0..11, not 0..12.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/pinctrl/sh-pfc/pfc-sh73a0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/sh-pfc/pfc-sh73a0.c b/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
index cd7c6645f7a47df1..d25e6f674d0aba84 100644
--- a/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
+++ b/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
@@ -2059,7 +2059,7 @@ static const unsigned int lcd2_data9_mux[] = {
LCD2D8_MARK,
};
static const unsigned int lcd2_data12_pins[] = {
- /* D[0:12] */
+ /* D[0:11] */
128, 129, 142, 143, 144, 145, 138, 139,
140, 141, 130, 131,
};
--
1.9.1
next prev parent reply other threads:[~2015-11-30 13:59 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 ` Geert Uytterhoeven [this message]
2016-02-04 18:53 ` [PATCH 0/3] pinctrl: sh-pfc: Correct pin range comments Laurent Pinchart
2016-02-08 15:36 ` 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=1448891996-5263-4-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--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).