docs: Fix a couple typos
This commit gets rid of some minor errors in Documentation/: * cputopology.txt: drawes -> drawers * debugging-via-ohci1394.txt: remove an unnecessary line break * static-keys: statemnts -> statements * zorro.txt: busses -> buses Signed-off-by: Stan Drozd <drozdziak1@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
1c4f128ed1
commit
9bb0e9cb04
@ -100,7 +100,7 @@ not defined by include/asm-XXX/topology.h:
|
|||||||
|
|
||||||
For architectures that don't support books (CONFIG_SCHED_BOOK) there are no
|
For architectures that don't support books (CONFIG_SCHED_BOOK) there are no
|
||||||
default definitions for topology_book_id() and topology_book_cpumask().
|
default definitions for topology_book_id() and topology_book_cpumask().
|
||||||
For architectures that don't support drawes (CONFIG_SCHED_DRAWER) there are
|
For architectures that don't support drawers (CONFIG_SCHED_DRAWER) there are
|
||||||
no default definitions for topology_drawer_id() and topology_drawer_cpumask().
|
no default definitions for topology_drawer_id() and topology_drawer_cpumask().
|
||||||
|
|
||||||
Additionally, CPU topology information is provided under
|
Additionally, CPU topology information is provided under
|
||||||
|
@ -100,8 +100,8 @@ Step-by-step instructions for using firescope with early OHCI initialization:
|
|||||||
CardBus and even some Express cards which are fully compliant to OHCI-1394
|
CardBus and even some Express cards which are fully compliant to OHCI-1394
|
||||||
specification are available. If it requires no driver for Windows operating
|
specification are available. If it requires no driver for Windows operating
|
||||||
systems, it most likely is. Only specialized shops have cards which are not
|
systems, it most likely is. Only specialized shops have cards which are not
|
||||||
compliant, they are based on TI PCILynx chips and require drivers for Win-
|
compliant, they are based on TI PCILynx chips and require drivers for Windows
|
||||||
dows operating systems.
|
operating systems.
|
||||||
|
|
||||||
The mentioned kernel log message contains the string "physUB" if the
|
The mentioned kernel log message contains the string "physUB" if the
|
||||||
controller implements a writable Physical Upper Bound register. This is
|
controller implements a writable Physical Upper Bound register. This is
|
||||||
|
@ -118,7 +118,7 @@ Or:
|
|||||||
|
|
||||||
Keys defined via DEFINE_STATIC_KEY_TRUE(), or DEFINE_STATIC_KEY_FALSE, may
|
Keys defined via DEFINE_STATIC_KEY_TRUE(), or DEFINE_STATIC_KEY_FALSE, may
|
||||||
be used in either static_branch_likely() or static_branch_unlikely()
|
be used in either static_branch_likely() or static_branch_unlikely()
|
||||||
statemnts.
|
statements.
|
||||||
|
|
||||||
Branch(es) can be set true via:
|
Branch(es) can be set true via:
|
||||||
|
|
||||||
|
@ -11,7 +11,7 @@ Last revised: September 5, 2003
|
|||||||
The Zorro bus is the bus used in the Amiga family of computers. Thanks to
|
The Zorro bus is the bus used in the Amiga family of computers. Thanks to
|
||||||
AutoConfig(tm), it's 100% Plug-and-Play.
|
AutoConfig(tm), it's 100% Plug-and-Play.
|
||||||
|
|
||||||
There are two types of Zorro busses, Zorro II and Zorro III:
|
There are two types of Zorro buses, Zorro II and Zorro III:
|
||||||
|
|
||||||
- The Zorro II address space is 24-bit and lies within the first 16 MB of the
|
- The Zorro II address space is 24-bit and lies within the first 16 MB of the
|
||||||
Amiga's address map.
|
Amiga's address map.
|
||||||
|
Loading…
Reference in New Issue
Block a user