* [PATCH 0/8] Replace some bad characters on documents
@ 2021-06-16 6:55 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
0 siblings, 2 replies; 3+ messages in thread
From: Mauro Carvalho Chehab @ 2021-06-16 6:55 UTC (permalink / raw)
To: Jonathan Corbet, Linux Doc Mailing List
Cc: Mauro Carvalho Chehab, linux-kernel, David S. Miller,
Theodore Ts'o, Alan Stern, Andreas Dilger, Jakub Kicinski,
Leo Yan, Mathieu Poirier, Mike Leach, Suzuki K Poulose,
Thorsten Leemhuis, coresight, intel-wired-lan, linux-arm-kernel,
linux-ext4, linux-pci, linux-usb, netdev
Hi Jon,
This series contain the remaining 8 patches I submitted at v3 that
weren't merged yet at -next.
This series is rebased on the top of your docs-next branch.
No changes here, except by some Reviewed/ack lines, and at the
name of the final patch (per PCI maintainer's request).
Mauro Carvalho Chehab (8):
docs: admin-guide: reporting-issues.rst: replace some characters
docs: trace: coresight: coresight-etm4x-reference.rst: replace some
characters
docs: driver-api: ioctl.rst: replace some characters
docs: usb: replace some characters
docs: vm: zswap.rst: replace some characters
docs: filesystems: ext4: blockgroup.rst: replace some characters
docs: networking: device_drivers: replace some characters
docs: PCI: Replace non-breaking spaces to avoid PDF issues
Documentation/PCI/acpi-info.rst | 18 +++++++++---------
Documentation/admin-guide/reporting-issues.rst | 2 +-
Documentation/driver-api/ioctl.rst | 8 ++++----
Documentation/filesystems/ext4/blockgroup.rst | 2 +-
.../device_drivers/ethernet/intel/i40e.rst | 6 +++---
.../device_drivers/ethernet/intel/iavf.rst | 2 +-
.../coresight/coresight-etm4x-reference.rst | 2 +-
Documentation/usb/ehci.rst | 2 +-
Documentation/usb/gadget_printer.rst | 2 +-
Documentation/vm/zswap.rst | 4 ++--
10 files changed, 24 insertions(+), 24 deletions(-)
--
2.31.1
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH 8/8] docs: PCI: Replace non-breaking spaces to avoid PDF issues
2021-06-16 6:55 [PATCH 0/8] Replace some bad characters on documents Mauro Carvalho Chehab
@ 2021-06-16 6:55 ` Mauro Carvalho Chehab
2021-06-17 19:35 ` [PATCH 0/8] Replace some bad characters on documents Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Mauro Carvalho Chehab @ 2021-06-16 6:55 UTC (permalink / raw)
To: Jonathan Corbet, Linux Doc Mailing List
Cc: Mauro Carvalho Chehab, Bjorn Helgaas, linux-kernel, linux-pci
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: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/PCI/acpi-info.rst | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/PCI/acpi-info.rst b/Documentation/PCI/acpi-info.rst
index 060217081c79..34c64a5a66ec 100644
--- a/Documentation/PCI/acpi-info.rst
+++ b/Documentation/PCI/acpi-info.rst
@@ -22,9 +22,9 @@ or if the device has INTx interrupts connected by platform interrupt
controllers and a _PRT is needed to describe those connections.
ACPI resource description is done via _CRS objects of devices in the ACPI
-namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
+namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
_CRS and figure out what resource is being consumed even if it doesn't have
-a driver for the device [3]. That's important because it means an old OS
+a driver for the device [3]. That's important because it means an old OS
can work correctly even on a system with new devices unknown to the OS.
The new devices might not do anything, but the OS can at least make sure no
resources conflict with them.
@@ -41,15 +41,15 @@ ACPI, that device will have a specific _HID/_CID that tells the OS what
driver to bind to it, and the _CRS tells the OS and the driver where the
device's registers are.
-PCI host bridges are PNP0A03 or PNP0A08 devices. Their _CRS should
-describe all the address space they consume. This includes all the windows
+PCI host bridges are PNP0A03 or PNP0A08 devices. Their _CRS should
+describe all the address space they consume. This includes all the windows
they forward down to the PCI bus, as well as registers of the host bridge
-itself that are not forwarded to PCI. The host bridge registers include
+itself that are not forwarded to PCI. The host bridge registers include
things like secondary/subordinate bus registers that determine the bus
range below the bridge, window registers that describe the apertures, etc.
These are all device-specific, non-architected things, so the only way a
PNP0A03/PNP0A08 driver can manage them is via _PRS/_CRS/_SRS, which contain
-the device-specific details. The host bridge registers also include ECAM
+the device-specific details. The host bridge registers also include ECAM
space, since it is consumed by the host bridge.
ACPI defines a Consumer/Producer bit to distinguish the bridge registers
@@ -66,7 +66,7 @@ the PNP0A03/PNP0A08 device itself. The workaround was to describe the
bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
With the exception of ECAM, the bridge register space is device-specific
anyway, so the generic PNP0A03/PNP0A08 driver (pci_root.c) has no need to
-know about it.
+know about it.
New architectures should be able to use "Consumer" Extended Address Space
descriptors in the PNP0A03 device for bridge registers, including ECAM,
@@ -75,9 +75,9 @@ ia64 kernels assume all address space descriptors, including "Consumer"
Extended Address Space ones, are windows, so it would not be safe to
describe bridge registers this way on those architectures.
-PNP0C02 "motherboard" devices are basically a catch-all. There's no
+PNP0C02 "motherboard" devices are basically a catch-all. There's no
programming model for them other than "don't use these resources for
-anything else." So a PNP0C02 _CRS should claim any address space that is
+anything else." So a PNP0C02 _CRS should claim any address space that is
(1) not claimed by _CRS under any other device object in the ACPI namespace
and (2) should not be assigned by the OS to something else.
--
2.31.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 0/8] Replace some bad characters on documents
2021-06-16 6:55 [PATCH 0/8] Replace some bad characters on documents 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 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2021-06-17 19:35 UTC (permalink / raw)
To: Mauro Carvalho Chehab, Linux Doc Mailing List
Cc: Mauro Carvalho Chehab, linux-kernel, David S. Miller,
Theodore Ts'o, Alan Stern, Andreas Dilger, Jakub Kicinski,
Leo Yan, Mathieu Poirier, Mike Leach, Suzuki K Poulose,
Thorsten Leemhuis, coresight, intel-wired-lan, linux-arm-kernel,
linux-ext4, linux-pci, linux-usb, netdev
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Hi Jon,
>
> This series contain the remaining 8 patches I submitted at v3 that
> weren't merged yet at -next.
>
> This series is rebased on the top of your docs-next branch.
>
> No changes here, except by some Reviewed/ack lines, and at the
> name of the final patch (per PCI maintainer's request).
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-06-17 19:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-16 6:55 [PATCH 0/8] Replace some bad characters on documents 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
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).