[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sh5196pk.fsf@purkki.adurom.net>
Date: Mon, 02 Jul 2018 15:12:55 +0300
From: Kalle Valo <kvalo@...eaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, kt.liao@....com.tw,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-input <linux-input@...r.kernel.org>,
ulrik.debie-os@...ig.org, phoenix@....com.tw,
aaron.ma@...onical.com, josh.chen@....com.tw
Subject: Re: [PATCH] Input: elantech - Fix V4 report decoding for module with middle key
Dmitry Torokhov <dmitry.torokhov@...il.com> writes:
> On July 1, 2018 5:00:03 PM PDT, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>On Sun, Jul 1, 2018 at 4:44 PM Dmitry Torokhov
>><dmitry.torokhov@...il.com> wrote:
>>>
>>> The reason it got messed up is I switched to pulling patches from
>>> patchwork.kernel.org as it collects Acked-by and Reviewed-by tags so
>>I
>>> do not have to add them manually, but unfortunately it does not do
>>> proper UTF-8:
>>
>>Ugh.
>>
>>I made an 'issue' of it for patchwork:
>>
>> https://github.com/getpatchwork/patchwork/issues/194
>>
>>and hopefully that can be fixed. It's sad when we corrupt names like
>>this.
>
> Might not even be an issue with recent patchwork, but unfortunately
> the version that is running on kernel.org is ancient as far as I know.
FWIW I use patchwork.kernel.org and I don't have any issues with UTF-8
characters in the From header. For example, here's one patch which I
recently applied:
https://git.kernel.org/linus/88001968245c
But of course it depends on what tools you use (I have my own patchwork
script which downloads and applies the patch) or what characters there
were etc.
Also I heard that we should get an upgrade to patchwork.kernel.org in
the near future, which is great. The current version has some quirks
which are quite annoying.
--
Kalle Valo
Powered by blists - more mailing lists