All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 3/8] docs: driver-api: ioctl.rst: replace some characters
Date: Wed, 16 Jun 2021 08:55:09 +0200	[thread overview]
Message-ID: <b2186e313f990488ded56d9b8d35a2d1fe479aa1.1623826294.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1623826294.git.mchehab+huawei@kernel.org>

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

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/driver-api/ioctl.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/driver-api/ioctl.rst b/Documentation/driver-api/ioctl.rst
index c455db0e1627..5b76e765827d 100644
--- a/Documentation/driver-api/ioctl.rst
+++ b/Documentation/driver-api/ioctl.rst
@@ -25,9 +25,9 @@ ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
 with the correct parameters:
 
 _IO/_IOR/_IOW/_IOWR
-   The macro name specifies how the argument will be used.  It may be a
+   The macro name specifies how the argument will be used.  It may be a
    pointer to data to be passed into the kernel (_IOW), out of the kernel
-   (_IOR), or both (_IOWR).  _IO can indicate either commands with no
+   (_IOR), or both (_IOWR).  _IO can indicate either commands with no
    argument or those passing an integer value instead of a pointer.
    It is recommended to only use _IO for commands without arguments,
    and use pointers for passing data.
@@ -200,10 +200,10 @@ cause an information leak, which can be used to defeat kernel address
 space layout randomization (KASLR), helping in an attack.
 
 For this reason (and for compat support) it is best to avoid any
-implicit padding in data structures.  Where there is implicit padding
+implicit padding in data structures.  Where there is implicit padding
 in an existing structure, kernel drivers must be careful to fully
 initialize an instance of the structure before copying it to user
-space.  This is usually done by calling memset() before assigning to
+space.  This is usually done by calling memset() before assigning to
 individual members.
 
 Subsystem abstractions
-- 
2.31.1


  parent reply	other threads:[~2021-06-16  6:55 UTC|newest]

Thread overview: 18+ 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 ` [Intel-wired-lan] " Mauro Carvalho Chehab
2021-06-16  6:55 ` 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   ` Mauro Carvalho Chehab
2021-06-16  6:55 ` Mauro Carvalho Chehab [this message]
2021-06-16  6:55 ` [PATCH 4/8] docs: usb: " Mauro Carvalho Chehab
2021-06-16  7:17   ` Greg Kroah-Hartman
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   ` [Intel-wired-lan] " 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
2021-06-17 19:35   ` [Intel-wired-lan] " Jonathan Corbet
2021-06-17 19:35   ` 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=b2186e313f990488ded56d9b8d35a2d1fe479aa1.1623826294.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.