From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 4/8] docs: usb: replace some characters
Date: Wed, 16 Jun 2021 09:17:59 +0200 [thread overview]
Message-ID: <YMmlpyxyfmum9r9O@kroah.com> (raw)
In-Reply-To: <0a4b0c38a9cd1133402a04a7ff60fefd9682d42e.1623826294.git.mchehab+huawei@kernel.org>
On Wed, Jun 16, 2021 at 08:55:10AM +0200, Mauro Carvalho Chehab wrote:
> The conversion tools used during DocBook/LaTeX/html/Markdown->ReST
> conversion and some cut-and-pasted text contain some characters that
> aren't easily reachable on standard keyboards and/or could cause
> troubles when parsed by the documentation build system.
>
> Replace the occurences of the following characters:
>
> - U+feff (''): BOM
> as it is not needed on UTF-8
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/usb/ehci.rst | 2 +-
> Documentation/usb/gadget_printer.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2021-06-16 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 6:55 [PATCH 0/8] Replace some bad characters on documents Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 1/8] docs: admin-guide: reporting-issues.rst: replace some characters Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 2/8] docs: trace: coresight: coresight-etm4x-reference.rst: " Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 3/8] docs: driver-api: ioctl.rst: " Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 4/8] docs: usb: " Mauro Carvalho Chehab
2021-06-16 7:17 ` Greg Kroah-Hartman [this message]
2021-06-16 6:55 ` [PATCH 5/8] docs: vm: zswap.rst: " Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 6/8] docs: filesystems: ext4: blockgroup.rst: " Mauro Carvalho Chehab
2021-06-16 14:53 ` Theodore Ts'o
2021-06-16 6:55 ` [PATCH 7/8] docs: networking: device_drivers: " Mauro Carvalho Chehab
2021-06-16 6:55 ` [PATCH 8/8] docs: PCI: Replace non-breaking spaces to avoid PDF issues Mauro Carvalho Chehab
2021-06-17 19:35 ` [PATCH 0/8] Replace some bad characters on documents 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=YMmlpyxyfmum9r9O@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=stern@rowland.harvard.edu \
/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).