From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 2/3] docs: firmware-guide: acpi: dsd: graph.rst: replace some characters
Date: Mon, 26 Jul 2021 15:00:27 +0300 [thread overview]
Message-ID: <20210726120027.GC3@paasikivi.fi.intel.com> (raw)
In-Reply-To: <a65b04a5cf341cff02d4b514dd4889b4fa4f94b8.1626947264.git.mchehab+huawei@kernel.org>
Hi Mauro,
On Thu, Jul 22, 2021 at 11:50:02AM +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+00a0 (' '): NO-BREAK SPACE
> as it can cause lines being truncated on PDF output
>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/firmware-guide/acpi/dsd/graph.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/firmware-guide/acpi/dsd/graph.rst b/Documentation/firmware-guide/acpi/dsd/graph.rst
> index 4341299aa937..0ced07cb1be3 100644
> --- a/Documentation/firmware-guide/acpi/dsd/graph.rst
> +++ b/Documentation/firmware-guide/acpi/dsd/graph.rst
> @@ -159,7 +159,7 @@ References
>
> [2] Devicetree. https://www.devicetree.org, referenced 2016-10-03.
>
> -[3] Documentation/devicetree/bindings/graph.txt
> +[3] Documentation/devicetree/bindings/graph.txt
I probably wrote this as a non-break space is produced by space + mod5,
preceded by opening bracket which also requires mod5.
The file is there but the file has moved to DT schema repository. I believe
the correct reference is:
https://github.com/devicetree-org/dt-schema/blob/master/schemas/graph.yaml
>
> [4] Device Properties UUID For _DSD.
> https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf,
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2021-07-26 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:50 [PATCH 0/3] Get rid of some undesirable characters Mauro Carvalho Chehab
2021-07-22 9:50 ` [PATCH 1/3] docs: sound: kernel-api: writing-an-alsa-driver.rst: replace some characters Mauro Carvalho Chehab
2021-07-22 9:50 ` [PATCH 2/3] docs: firmware-guide: acpi: dsd: graph.rst: " Mauro Carvalho Chehab
2021-07-26 12:00 ` Sakari Ailus [this message]
2021-07-22 9:50 ` [PATCH 3/3] docs: virt: kvm: api.rst: " Mauro Carvalho Chehab
2021-07-26 12:26 ` Paolo Bonzini
2021-07-25 20:36 ` [PATCH 0/3] Get rid of some undesirable characters 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=20210726120027.GC3@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=vishal.l.verma@intel.com \
/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).