On Thu, Jan 29, 2015 at 11:12 AM, Geert Uytterhoeven <geert+renesas@xxxxxxxxx> wrote: > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > 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? This is painful, your patch arrives with this header: Content-Type: text/plain; charset=y Content-Transfer-Encoding: 8bit When I try to apply it git am says: $ git am --signoff geert1.patch fatal: cannot convert from y to UTF-8 Wut? I never heard of an encoding named "y", and SMTP is not my strongest subject anyway. This UTF-8 business i becoming a subject for this years kernel summit as I see the same thing with a few fellow german and Swedish contributors appearing using our funny diacritics ÅÄÖÆØåäöøæ Yeah well even ß at some time IIRC... Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html