linux-kernel - Re: [PATCH RFC] perf/callchain: fixup charset file header

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 22 May 2017 14:52:25 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Nicholas Mc Guire <der.herr@...r.at>
Cc:     Markus Kreidl <mkreidl@...ntech.at>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Paul Mackerras <paulus@....ibm.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] perf/callchain: fixup charset file header

On Sat, May 20, 2017 at 06:47:31PM +0200, Nicholas Mc Guire wrote:
> Non-UTF-8 characters are a problem for some terminals and also
> make greping harder than necessary - this only switches the
> copyright sign to the common (C).
> 
> Reported-by: Markus Kreidl <mkreidl@...ntech.at>
> Signed-off-by: Nicholas Mc Guire <der.herr@...r.at>
> ---
> 
> Found by checkpatch --strict:
> CHECK: Invalid UTF-8, patch and commit message should be encoded in UTF-8
> #7: FILE: kernel/events/callchain.c:7:
> + *  Copyright  ?  2009 Paul Mackerras, IBM Corp. <paulus@....ibm.com>
> 
> Before I start generating sets of patches that fix encoding issues 
> I would like to know if that is going to be accepted at all - the
> background is that it causes quite a bit of trouble when automating
> tools if these encoding problems make using simple tools hard (e.g.
> grep) and thus make automation a lot more complicated that necessary.
> It seems to me that the codingstyle does not mandate UTF-8 but there
> are a few places where it is "suggested" like in:
>   Documentation/process/email-clients.rst

The last discussion on the subject was:

http://lkml.iu.edu/hypermail/linux/kernel/1001.2/02928.html

Which seemed to suggest replacing it with the UTF8 equivalent glyph. I
can't remember a patch, not Paul Ack'ing it (which is very much required
in order to change his copyright message).