linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] proc: fixup (c) sign
Date: Thu, 12 Apr 2018 01:50:29 +0100	[thread overview]
Message-ID: <20180412005029.GQ30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFxrpn=GdgqgrczUdj-wndFdQvmfytwMiYL5=TQWhfpAjA@mail.gmail.com>

On Wed, Apr 11, 2018 at 03:41:26PM -0700, Linus Torvalds wrote:
> On Wed, Apr 11, 2018 at 1:24 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> >
> > It got sent from here as iso8859-1.
> 
> It's probably a good idea to just move away from Latin1 entirely, and
> encourage people to just use utf-8.
> 
> But yes, Andrew's scripts clearly do a horrible job at looking at
> email encoding, and that really should be fixed.
> 
> I worry less about silly copyright signs than about peoples actual
> _names_, but we've certainly seen problems there too.

FWIW, excluding the stuff obviously not in UTF8 (logo.gif and 
tools/power/cpupower/po/{de,fr}.po) we have

lib/fonts/font_7x14.c
lib/fonts/font_8x16.c
lib/fonts/font_8x8.c
lib/fonts/font_pearl_8x8.c
arch/s390/kernel/ebcdic.c
	crap in comments
arch/m68k/hp300/hp300map.map
drivers/tty/vt/defkeymap.map
	non-UTF8 - literals for compose statements
arch/arm/crypto/sha256_glue.c
arch/arm/crypto/sha256_neon_glue.c
kernel/events/callchain.c
	Latin1 copyright symbol (0xa9)
drivers/staging/rtl8188eu/include/odm.h
	Latin1 inverted ! (0xa1)
Documentation/devicetree/bindings/net/nfc/pn544.txt
	Latin1 superscript 2 (0xb2), in I²C
arch/arm/boot/dts/sun4i-a10-inet97fv2.dts
	Latin1 o-umlaut (0xf6) in David Lanzendörfer
drivers/crypto/vmx/ghashp8-ppc.pl
	a bunch of Latin1 middle dots (0xb7), in comments inside string constant
used to produce asm output, no less
drivers/gpu/drm/amd/include/atombios.h
	several U+FFFD in there - buggered conversion to UTF8?
drivers/gpu/drm/r128/r128_drv.h
	ditto, but here it's possible to figure out what got buggered -
Michel D�zer <daenzerm@student.ethz.ch> that presumably should've been "Dänzer"
drivers/iio/dac/ltc2632.c
	Latin1 e-acute in Maxime Roussin-Bélanger
drivers/power/reset/ltc2952-poweroff.c
	ditto in René Moll
drivers/spi/spi-omap-100k.c
	a couple of U+FFFD in Juha Yrjölä <juha.yrjola@nokia.com> - o- and a-umlaut
In this case the actual spelling is trivially googled.
drivers/spi/spi-omap2-mcspi.c
	ditto
drivers/usb/misc/iowarrior.c
	U+FFFD in Stéphane Doyon <s.doyon@videotron.ca> - e-acute
drivers/visorbus/visorbus_main.c
	U+FFFD in place of copyright symbol

  parent reply	other threads:[~2018-04-12  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 22:41 [PATCH] proc: fixup (c) sign Linus Torvalds
2018-04-11 23:17 ` Andrew Morton
2018-04-12  0:50 ` Al Viro [this message]
2018-04-12 17:14 Linus Torvalds
2018-04-12 19:50 ` Alexey Dobriyan
2018-04-12 20:16   ` 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=20180412005029.GQ30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).