From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Niklas Söderlund" <niso@kth.se>,
linux-gpio@vger.kernel.org, linux-sh@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>
Subject: [PATCH] sh-pfc: emev2 - Fix mangled author name
Date: Thu, 29 Jan 2015 11:12:56 +0100 [thread overview]
Message-ID: <1422526376-12146-1-git-send-email-geert+renesas@glider.be> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1145 bytes --]
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Fixes: 1e7d5d849cf4f0c5 ("sh-pfc: Add emev2 pinmux support")
---
Looks like the original UTF-8 was interpreted as ISO-8859-1, and the
resulting characters being converted to UTF-8 again.
BTW, the same issue is present in the SoB-lines of both
1e7d5d849cf4f0c5 ("sh-pfc: Add emev2 pinmux support") and
4c9e473541c52453 ("sh-pfc: add macro to define pinmux without function")
Perhaps they can still be fixed while squashing this in?
---
drivers/pinctrl/sh-pfc/pfc-emev2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/sh-pfc/pfc-emev2.c b/drivers/pinctrl/sh-pfc/pfc-emev2.c
index 9b3ce5d1265b391f..849c6943ed308ee0 100644
--- a/drivers/pinctrl/sh-pfc/pfc-emev2.c
+++ b/drivers/pinctrl/sh-pfc/pfc-emev2.c
@@ -1,7 +1,7 @@
/*
* Pin Function Controller Support
*
- * Copyright (C) 2015 Niklas Söderlund
+ * Copyright (C) 2015 Niklas Söderlund
*
* This file is subject to the terms and conditions of the GNU General Public
* License. See the file "COPYING" in the main directory of this archive
--
1.9.1
next reply other threads:[~2015-01-29 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 10:12 Geert Uytterhoeven [this message]
2015-02-04 8:54 ` [PATCH] sh-pfc: emev2 - Fix mangled author name Linus Walleij
2015-02-04 9:02 ` Geert Uytterhoeven
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=1422526376-12146-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=niso@kth.se \
/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).