mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Andy Whitcroft <apw@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v2] checkpatch: Only encode UTF-8 quoted printable mail headers
Date: Thu, 19 Jul 2018 10:38:44 -0700	[thread overview]
Message-ID: <e03d364551b205afeef5b1702efec9eedef388f6.camel@perches.com> (raw)
In-Reply-To: <CAMuHMdWCjr__9QB-wSiuo7ZZnOc9PuCRLJU=cVTrfvywJh5eBg@mail.gmail.com>

On Thu, 2018-07-19 at 17:03 +0200, Geert Uytterhoeven wrote:
> Hi Arnd,
> 
> On Thu, Jul 19, 2018 at 4:50 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On a related note, I've looked through all files in the kernel, and found
> > that very file files in there are something other than 7-bit ASCII, UTF-8
> > or non-text files (according to /usr/bin/file). These are the only ones I found:
> > 
> > Documentation/devicetree/bindings/net/nfc/pn544.txt: ISO-8859 text
> > arch/arm/boot/dts/sun4i-a10-inet97fv2.dts:           C source, ISO-8859 text
> > arch/arm/crypto/sha256_glue.c:                       C source, ISO-8859 text
> > arch/arm/crypto/sha256_neon_glue.c:                  C source, ISO-8859 text
> > arch/m68k/hp300/hp300map.map:                        ISO-8859 text
> > arch/s390/kernel/ebcdic.c:                           C source, Non-ISO
> > extended-ASCII text
> > drivers/crypto/vmx/ghashp8-ppc.pl:                   a /usr/bin/env
> > perl script, ISO-8859 text executable
> > drivers/iio/dac/ltc2632.c:                           C source, ISO-8859 text
> > drivers/power/reset/ltc2952-poweroff.c:              C source, ISO-8859 text
> > drivers/staging/rtl8188eu/include/odm.h:             C source, ISO-8859 text
> > drivers/tty/vt/defkeymap.map:                        ISO-8859 text
> > kernel/events/callchain.c:                           C source, ISO-8859 text
> > lib/fonts/font_7x14.c:                               data
> > lib/fonts/font_8x16.c:                               data
> > lib/fonts/font_8x8.c:                                data
> > lib/fonts/font_pearl_8x8.c:                          data
> > net/netfilter/ipvs/Kconfig:                          ISO-8859 text
> > net/netfilter/ipvs/ip_vs_mh.c:                       C source, ISO-8859 text
> > tools/power/cpupower/po/de.po:                       GNU gettext
> > message catalogue, ISO-8859 text
> > tools/power/cpupower/po/fr.po:                       GNU gettext
> > message catalogue, ISO-8859 text
> > 
> > Almost all of those can be trivially converted using 'recode ISO-8859-1..UTF-8',
> > which we should probably do. The four font files contain comments for each
> > of the 256 characters, so that recode turns e.g. the <FF> character
> > into <U+00FF>,
> > which is probably still what we want here.
> > 
> > The one exception seems to be arch/s390/kernel/ebcdic.c, which apparently
> > uses 0x81 bytes as an excape before characters ISO-8859-1 characters with
> > the high bit set. I don't know what that encoding is called, but I managed
> > to manually convert it into something useful.
> 
> Yes, we should convert everything to UTF-8.

Thanks.

Can you send a patch or a script for Linus to apply?


  reply	other threads:[~2018-07-19 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 14:52 Geert Uytterhoeven
2018-07-18 21:42 ` Andrew Morton
2018-07-18 21:55   ` Joe Perches
2018-07-19 14:50 ` Arnd Bergmann
2018-07-19 15:03   ` Geert Uytterhoeven
2018-07-19 17:38     ` Joe Perches [this message]
2018-07-24 11:19       ` Arnd Bergmann

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=e03d364551b205afeef5b1702efec9eedef388f6.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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®