From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>,
Jakub Kicinski <kuba@kernel.org>,
Jean Delvare <jdelvare@suse.com>, Jens Axboe <axboe@kernel.dk>,
intel-wired-lan@lists.osuosl.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH 0/5] Fix some UTF-8 bad usages
Date: Tue, 11 May 2021 17:01:27 +0200 [thread overview]
Message-ID: <cover.1620744606.git.mchehab+huawei@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1720 bytes --]
This series follow up this past series:
https://lore.kernel.org/lkml/cover.1620641727.git.mchehab+huawei@kernel.org/
Containing just the manual fixes from it. I'll respin the remaining
patches on a separate series.
Please note that patches 1 to 3 are identical to the ones posted
on the original series.
Patch 1 is special: it fixes some left-overs from a convertion
from cdrom-standard.tex: there, some characters that are
valid in C were converted to some visually similar UTF-8 by LaTeX.
Patch 2 remove U+00ac ('¬'): NOT SIGN characters at the end of
the first line of two files. No idea why those ended being there :-p
Patch 3 replaces:
KernelVersion:»·3.3
by:
KernelVersion: 3.3
which is the expected format for the KernelVersion field;
Patches 4 and 5 fix some bad usages of EM DASH/EN DASH on
places that it should be, instead, a normal hyphen. I suspect
that they ended being there due to the usage of some conversion
toolset.
Mauro Carvalho Chehab (5):
docs: cdrom-standard.rst: get rid of uneeded UTF-8 chars
docs: ABI: remove a meaningless UTF-8 character
docs: ABI: remove some spurious characters
docs: hwmon: tmp103.rst: fix bad usage of UTF-8 chars
docs: networking: device_drivers: fix bad usage of UTF-8 chars
.../obsolete/sysfs-kernel-fadump_registered | 2 +-
.../obsolete/sysfs-kernel-fadump_release_mem | 2 +-
Documentation/ABI/testing/sysfs-module | 4 +--
Documentation/cdrom/cdrom-standard.rst | 30 +++++++++----------
Documentation/hwmon/tmp103.rst | 4 +--
.../device_drivers/ethernet/intel/i40e.rst | 4 +--
.../device_drivers/ethernet/intel/iavf.rst | 2 +-
7 files changed, 24 insertions(+), 24 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-11 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:01 Mauro Carvalho Chehab [this message]
2021-05-11 15:01 ` [PATCH 5/5] docs: networking: device_drivers: fix bad usage of UTF-8 chars Mauro Carvalho Chehab
2021-05-11 17:22 ` Andrew Lunn
2021-05-11 18:24 ` Jonathan Corbet
2021-05-11 18:48 ` Matthew Wilcox
2021-05-11 19:10 ` Mauro Carvalho Chehab
2021-05-11 17:01 ` [PATCH 0/5] Fix some UTF-8 bad usages Jonathan Corbet
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=cover.1620744606.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.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).