From: Kalle Valo <kvalo@codeaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kt.liao@emc.com.tw,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input <linux-input@vger.kernel.org>,
ulrik.debie-os@e2big.org, phoenix@emc.com.tw,
aaron.ma@canonical.com, josh.chen@emc.com.tw
Subject: Re: [PATCH] Input: elantech - Fix V4 report decoding for module with middle key
Date: Mon, 02 Jul 2018 15:12:55 +0300 [thread overview]
Message-ID: <87sh5196pk.fsf@purkki.adurom.net> (raw)
In-Reply-To: <A5DA555C-6131-4F7B-82F2-A06C12E23CAF@gmail.com> (Dmitry Torokhov's message of "Sun, 01 Jul 2018 17:12:37 -0700")
Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:
> On July 1, 2018 5:00:03 PM PDT, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>>On Sun, Jul 1, 2018 at 4:44 PM Dmitry Torokhov
>><dmitry.torokhov@gmail.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
next prev parent reply other threads:[~2018-07-02 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 11:33 KT Liao
2018-05-29 18:05 ` Dmitry Torokhov
2018-05-30 7:03 ` 廖崇榮
2018-06-22 0:16 ` 'Dmitry Torokhov'
2018-07-01 23:30 ` Linus Torvalds
2018-07-01 23:44 ` Dmitry Torokhov
2018-07-02 0:00 ` Linus Torvalds
2018-07-02 0:12 ` Dmitry Torokhov
2018-07-02 12:12 ` Kalle Valo [this message]
2018-07-02 15:32 ` Randy Dunlap
2018-07-02 16:31 ` Linus Torvalds
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=87sh5196pk.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=aaron.ma@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=josh.chen@emc.com.tw \
--cc=kt.liao@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phoenix@emc.com.tw \
--cc=torvalds@linux-foundation.org \
--cc=ulrik.debie-os@e2big.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
all inboxes | Powered by JetHome®