* [PATCH] [trivial] Documentation: Fix multiple typo in Documentation
@ 2012-03-04 14:16 Masanari Iida
2012-03-04 17:06 ` Randy Dunlap
0 siblings, 1 reply; 5+ messages in thread
From: Masanari Iida @ 2012-03-04 14:16 UTC (permalink / raw)
To: rdunlap, linux-doc; +Cc: trivial, linux-kernel, Masanari Iida
Correct following typo within 17 files in Documentation.
"specifing" to "specifying" in vm/unevictable-lru.txt
"subjet" to "subject" in security/Smack.txt
"fulfil" to "fulfill" in security/keys.txt
"symmetic" to "symmetric" in security/keys-trusted-encrypted.txt
"Refererence" to "Reference" in device-mapper/dm-raid.txt
"strutures" to "structures" in device-mapper/persistent-data.txt
"attribude" to "attribute" in kbuild/kconfig-language.txt
"satisified" to "satisfied" in virtual/kvm/mmu.txt
"artificically" to "artificially" in virtual/kvm/mmu.txt
"hierarhical" to "hierarchical" in cgroups/blkio-controller.txt
"hierarhcy" to "hierarchy" in cgroups/blkio-controller.txt
"exising" to "existing" in cgroups/blkio-controller.txt
"deivce" to "device" in cgroups/blkio-controller.txt
"subjectd" to "subjected" in cgroups/blkio-contoller.txt
"Priorty" to "Priority" in filesystem/ext4.txt
"systme" to "system" in filesystem/ext4.txt
"fileystem" to "filesystem" in filesystem/gfs2-uevents.txt
"returing" to "returning" in filesystem/vfs.txt
"practise" to "practice" in devicetree/booting-without-of.txt
"evalutation" to "evaluation" in devicetree/bindings/arm/sirf.txt
"adresse" to "address" in devicetree/bindings/arm/omap/omap.txt
"shedule" to "schedule" in ABI/obsolete/sysfs-class-rfkill
"dyanmic" to "dynamic" in ABI/stable/sysfs-module
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
---
Documentation/ABI/obsolete/sysfs-class-rfkill | 2 +-
Documentation/ABI/stable/sysfs-module | 2 +-
Documentation/cgroups/blkio-controller.txt | 18 +++++++++---------
Documentation/device-mapper/dm-raid.txt | 2 +-
Documentation/device-mapper/persistent-data.txt | 2 +-
.../devicetree/bindings/arm/omap/omap.txt | 2 +-
Documentation/devicetree/bindings/arm/sirf.txt | 2 +-
Documentation/devicetree/booting-without-of.txt | 2 +-
Documentation/filesystems/ext4.txt | 4 ++--
Documentation/filesystems/gfs2-uevents.txt | 2 +-
Documentation/filesystems/vfs.txt | 2 +-
Documentation/kbuild/kconfig-language.txt | 2 +-
Documentation/security/Smack.txt | 2 +-
Documentation/security/keys-trusted-encrypted.txt | 2 +-
Documentation/security/keys.txt | 2 +-
Documentation/virtual/kvm/mmu.txt | 4 ++--
Documentation/vm/unevictable-lru.txt | 2 +-
17 files changed, 27 insertions(+), 27 deletions(-)
diff --git a/Documentation/ABI/obsolete/sysfs-class-rfkill b/Documentation/ABI/obsolete/sysfs-class-rfkill
index 4201d5b..ff60ad9 100644
--- a/Documentation/ABI/obsolete/sysfs-class-rfkill
+++ b/Documentation/ABI/obsolete/sysfs-class-rfkill
@@ -7,7 +7,7 @@ Date: 09-Jul-2007
KernelVersion v2.6.22
Contact: linux-wireless@vger.kernel.org
Description: Current state of the transmitter.
- This file is deprecated and sheduled to be removed in 2014,
+ This file is deprecated and scheduled to be removed in 2014,
because its not possible to express the 'soft and hard block'
state of the rfkill driver.
Values: A numeric value.
diff --git a/Documentation/ABI/stable/sysfs-module b/Documentation/ABI/stable/sysfs-module
index 75be431..a0dd21c 100644
--- a/Documentation/ABI/stable/sysfs-module
+++ b/Documentation/ABI/stable/sysfs-module
@@ -6,7 +6,7 @@ Description:
The name of the module that is in the kernel. This
module name will show up either if the module is built
directly into the kernel, or if it is loaded as a
- dyanmic module.
+ dynamic module.
/sys/module/MODULENAME/parameters
This directory contains individual files that are each
diff --git a/Documentation/cgroups/blkio-controller.txt b/Documentation/cgroups/blkio-controller.txt
index 84f0a15..b4b1fb3 100644
--- a/Documentation/cgroups/blkio-controller.txt
+++ b/Documentation/cgroups/blkio-controller.txt
@@ -94,11 +94,11 @@ Throttling/Upper Limit policy
Hierarchical Cgroups
====================
-- Currently none of the IO control policy supports hierarhical groups. But
- cgroup interface does allow creation of hierarhical cgroups and internally
+- Currently none of the IO control policy supports hierarchical groups. But
+ cgroup interface does allow creation of hierarchical cgroups and internally
IO policies treat them as flat hierarchy.
- So this patch will allow creation of cgroup hierarhcy but at the backend
+ So this patch will allow creation of cgroup hierarchcy but at the backend
everything will be treated as flat. So if somebody created a hierarchy like
as follows.
@@ -266,7 +266,7 @@ Proportional weight policy files
- blkio.idle_time
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
This is the amount of time spent by the IO scheduler idling for a
- given cgroup in anticipation of a better request than the exising ones
+ given cgroup in anticipation of a better request than the existing ones
from other queues/cgroups. This is in nanoseconds. If this is read
when the cgroup is in an idling state, the stat will only report the
idle_time accumulated till the last idle period and will not include
@@ -283,34 +283,34 @@ Throttling/Upper limit policy files
-----------------------------------
- blkio.throttle.read_bps_device
- Specifies upper limit on READ rate from the device. IO rate is
- specified in bytes per second. Rules are per deivce. Following is
+ specified in bytes per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
- blkio.throttle.write_bps_device
- Specifies upper limit on WRITE rate to the device. IO rate is
- specified in bytes per second. Rules are per deivce. Following is
+ specified in bytes per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
- blkio.throttle.read_iops_device
- Specifies upper limit on READ rate from the device. IO rate is
- specified in IO per second. Rules are per deivce. Following is
+ specified in IO per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
- blkio.throttle.write_iops_device
- Specifies upper limit on WRITE rate to the device. IO rate is
- specified in io per second. Rules are per deivce. Following is
+ specified in io per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
Note: If both BW and IOPS rules are specified for a device, then IO is
- subjectd to both the constraints.
+ subjected to both the constraints.
- blkio.throttle.io_serviced
- Number of IOs (bio) completed to/from the disk by the group (as
diff --git a/Documentation/device-mapper/dm-raid.txt b/Documentation/device-mapper/dm-raid.txt
index 2a8c113..946c733 100644
--- a/Documentation/device-mapper/dm-raid.txt
+++ b/Documentation/device-mapper/dm-raid.txt
@@ -28,7 +28,7 @@ The target is named "raid" and it accepts the following parameters:
raid6_nc RAID6 N continue
- rotating parity N (right-to-left) with data continuation
- Refererence: Chapter 4 of
+ Reference: Chapter 4 of
http://www.snia.org/sites/default/files/SNIA_DDF_Technical_Position_v2.0.pdf
<#raid_params>: The number of parameters that follow.
diff --git a/Documentation/device-mapper/persistent-data.txt b/Documentation/device-mapper/persistent-data.txt
index 0e5df9b..a333bcb 100644
--- a/Documentation/device-mapper/persistent-data.txt
+++ b/Documentation/device-mapper/persistent-data.txt
@@ -3,7 +3,7 @@ Introduction
The more-sophisticated device-mapper targets require complex metadata
that is managed in kernel. In late 2010 we were seeing that various
-different targets were rolling their own data strutures, for example:
+different targets were rolling their own data structures, for example:
- Mikulas Patocka's multisnap implementation
- Heinz Mauelshagen's thin provisioning target
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
index ce78498..e78e8bc 100644
--- a/Documentation/devicetree/bindings/arm/omap/omap.txt
+++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
@@ -5,7 +5,7 @@ IPs present in the SoC.
On top of that an omap_device is created to extend the platform_device
capabilities and to allow binding with one or several hwmods.
The hwmods will contain all the information to build the device:
-adresse range, irq lines, dma lines, interconnect, PRCM register,
+address range, irq lines, dma lines, interconnect, PRCM register,
clock domain, input clocks.
For the moment just point to the existing hwmod, the next step will be
to move data from hwmod to device-tree representation.
diff --git a/Documentation/devicetree/bindings/arm/sirf.txt b/Documentation/devicetree/bindings/arm/sirf.txt
index 6b07f65..1881e1c 100644
--- a/Documentation/devicetree/bindings/arm/sirf.txt
+++ b/Documentation/devicetree/bindings/arm/sirf.txt
@@ -1,3 +1,3 @@
-prima2 "cb" evalutation board
+prima2 "cb" evaluation board
Required root node properties:
- compatible = "sirf,prima2-cb", "sirf,prima2";
diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt
index 7c1329d..da0bfeb 100644
--- a/Documentation/devicetree/booting-without-of.txt
+++ b/Documentation/devicetree/booting-without-of.txt
@@ -169,7 +169,7 @@ it with special cases.
b) Entry with a flattened device-tree block. Firmware loads the
physical address of the flattened device tree block (dtb) into r2,
- r1 is not used, but it is considered good practise to use a valid
+ r1 is not used, but it is considered good practice to use a valid
machine number as described in Documentation/arm/Booting.
r0 : 0
diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt
index 990219c..1b7f9ac 100644
--- a/Documentation/filesystems/ext4.txt
+++ b/Documentation/filesystems/ext4.txt
@@ -305,7 +305,7 @@ min_batch_time=usec This parameter sets the commit time (as
fast disks, at the cost of increasing latency.
journal_ioprio=prio The I/O priority (from 0 to 7, where 0 is the
- highest priorty) which should be used for I/O
+ highest priority) which should be used for I/O
operations submitted by kjournald2 during a
commit operation. This defaults to 3, which is
a slightly higher priority than the default I/O
@@ -340,7 +340,7 @@ noinit_itable Do not initialize any uninitialized inode table
init_itable=n The lazy itable init code will wait n times the
number of milliseconds it took to zero out the
previous block group's inode table. This
- minimizes the impact on the systme performance
+ minimizes the impact on the system performance
while file system's inode table is being initialized.
discard Controls whether ext4 should issue discard/TRIM
diff --git a/Documentation/filesystems/gfs2-uevents.txt b/Documentation/filesystems/gfs2-uevents.txt
index d818896..19a19eb 100644
--- a/Documentation/filesystems/gfs2-uevents.txt
+++ b/Documentation/filesystems/gfs2-uevents.txt
@@ -62,7 +62,7 @@ be fixed.
The REMOVE uevent is generated at the end of an unsuccessful mount
or at the end of a umount of the filesystem. All REMOVE uevents will
-have been preceded by at least an ADD uevent for the same fileystem,
+have been preceded by at least an ADD uevent for the same filesystem,
and unlike the other uevents is generated automatically by the kernel's
kobject subsystem.
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 3d9393b..e916e3d 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -993,7 +993,7 @@ struct dentry_operations {
If the 'rcu_walk' parameter is true, then the caller is doing a
pathwalk in RCU-walk mode. Sleeping is not permitted in this mode,
- and the caller can be asked to leave it and call again by returing
+ and the caller can be asked to leave it and call again by returning
-ECHILD.
This function is only used if DCACHE_MANAGE_TRANSIT is set on the
diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
index 44e2649..a686f9c 100644
--- a/Documentation/kbuild/kconfig-language.txt
+++ b/Documentation/kbuild/kconfig-language.txt
@@ -117,7 +117,7 @@ applicable everywhere (see syntax).
This attribute is only applicable to menu blocks, if the condition is
false, the menu block is not displayed to the user (the symbols
contained there can still be selected by other symbols, though). It is
- similar to a conditional "prompt" attribude for individual menu
+ similar to a conditional "prompt" attribute for individual menu
entries. Default value of "visible" is true.
- numerical ranges: "range" <symbol> <symbol> ["if" <expr>]
diff --git a/Documentation/security/Smack.txt b/Documentation/security/Smack.txt
index e9dab41..d2f72ae 100644
--- a/Documentation/security/Smack.txt
+++ b/Documentation/security/Smack.txt
@@ -536,6 +536,6 @@ writing a single character to the /smack/logging file :
3 : log denied & accepted
Events are logged as 'key=value' pairs, for each event you at least will get
-the subjet, the object, the rights requested, the action, the kernel function
+the subject, the object, the rights requested, the action, the kernel function
that triggered the event, plus other pairs depending on the type of event
audited.
diff --git a/Documentation/security/keys-trusted-encrypted.txt b/Documentation/security/keys-trusted-encrypted.txt
index c9e4855..e105ae9 100644
--- a/Documentation/security/keys-trusted-encrypted.txt
+++ b/Documentation/security/keys-trusted-encrypted.txt
@@ -1,7 +1,7 @@
Trusted and Encrypted Keys
Trusted and Encrypted Keys are two new key types added to the existing kernel
-key ring service. Both of these new types are variable length symmetic keys,
+key ring service. Both of these new types are variable length symmetric keys,
and in both cases all keys are created in the kernel, and user space sees,
stores, and loads only encrypted blobs. Trusted Keys require the availability
of a Trusted Platform Module (TPM) chip for greater security, while Encrypted
diff --git a/Documentation/security/keys.txt b/Documentation/security/keys.txt
index 713ec23..7877170 100644
--- a/Documentation/security/keys.txt
+++ b/Documentation/security/keys.txt
@@ -672,7 +672,7 @@ The keyctl syscall functions are:
If the kernel calls back to userspace to complete the instantiation of a
key, userspace should use this call mark the key as negative before the
- invoked process returns if it is unable to fulfil the request.
+ invoked process returns if it is unable to fulfill the request.
The process must have write access on the key to be able to instantiate
it, and the key must be uninstantiated.
diff --git a/Documentation/virtual/kvm/mmu.txt b/Documentation/virtual/kvm/mmu.txt
index 5dc972c..fa5f1db 100644
--- a/Documentation/virtual/kvm/mmu.txt
+++ b/Documentation/virtual/kvm/mmu.txt
@@ -347,7 +347,7 @@ To instantiate a large spte, four constraints must be satisfied:
- the spte must point to a large host page
- the guest pte must be a large pte of at least equivalent size (if tdp is
- enabled, there is no guest pte and this condition is satisified)
+ enabled, there is no guest pte and this condition is satisfied)
- if the spte will be writeable, the large page frame may not overlap any
write-protected pages
- the guest page must be wholly contained by a single memory slot
@@ -356,7 +356,7 @@ To check the last two conditions, the mmu maintains a ->write_count set of
arrays for each memory slot and large page size. Every write protected page
causes its write_count to be incremented, thus preventing instantiation of
a large spte. The frames at the end of an unaligned memory slot have
-artificically inflated ->write_counts so they can never be instantiated.
+artificially inflated ->write_counts so they can never be instantiated.
Further reading
===============
diff --git a/Documentation/vm/unevictable-lru.txt b/Documentation/vm/unevictable-lru.txt
index 609d1a3..fa206cc 100644
--- a/Documentation/vm/unevictable-lru.txt
+++ b/Documentation/vm/unevictable-lru.txt
@@ -619,7 +619,7 @@ all PTEs from the page. For this purpose, the unevictable/mlock infrastructure
introduced a variant of try_to_unmap() called try_to_munlock().
try_to_munlock() calls the same functions as try_to_unmap() for anonymous and
-mapped file pages with an additional argument specifing unlock versus unmap
+mapped file pages with an additional argument specifying unlock versus unmap
processing. Again, these functions walk the respective reverse maps looking
for VM_LOCKED VMAs. When such a VMA is found for anonymous pages and file
pages mapped in linear VMAs, as in the try_to_unmap() case, the functions
--
1.7.9.2.262.gba998
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] [trivial] Documentation: Fix multiple typo in Documentation
2012-03-04 14:16 [PATCH] [trivial] Documentation: Fix multiple typo in Documentation Masanari Iida
@ 2012-03-04 17:06 ` Randy Dunlap
0 siblings, 0 replies; 5+ messages in thread
From: Randy Dunlap @ 2012-03-04 17:06 UTC (permalink / raw)
To: Masanari Iida; +Cc: linux-doc, trivial, linux-kernel
On 03/04/2012 06:16 AM, Masanari Iida wrote:
> Correct following typo within 17 files in Documentation.
>
> "specifing" to "specifying" in vm/unevictable-lru.txt
> "subjet" to "subject" in security/Smack.txt
> "fulfil" to "fulfill" in security/keys.txt
> "symmetic" to "symmetric" in security/keys-trusted-encrypted.txt
> "Refererence" to "Reference" in device-mapper/dm-raid.txt
> "strutures" to "structures" in device-mapper/persistent-data.txt
> "attribude" to "attribute" in kbuild/kconfig-language.txt
> "satisified" to "satisfied" in virtual/kvm/mmu.txt
> "artificically" to "artificially" in virtual/kvm/mmu.txt
> "hierarhical" to "hierarchical" in cgroups/blkio-controller.txt
> "hierarhcy" to "hierarchy" in cgroups/blkio-controller.txt
> "exising" to "existing" in cgroups/blkio-controller.txt
> "deivce" to "device" in cgroups/blkio-controller.txt
> "subjectd" to "subjected" in cgroups/blkio-contoller.txt
> "Priorty" to "Priority" in filesystem/ext4.txt
> "systme" to "system" in filesystem/ext4.txt
> "fileystem" to "filesystem" in filesystem/gfs2-uevents.txt
> "returing" to "returning" in filesystem/vfs.txt
> "practise" to "practice" in devicetree/booting-without-of.txt
> "evalutation" to "evaluation" in devicetree/bindings/arm/sirf.txt
> "adresse" to "address" in devicetree/bindings/arm/omap/omap.txt
> "shedule" to "schedule" in ABI/obsolete/sysfs-class-rfkill
> "dyanmic" to "dynamic" in ABI/stable/sysfs-module
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
> ---
> Documentation/ABI/obsolete/sysfs-class-rfkill | 2 +-
> Documentation/ABI/stable/sysfs-module | 2 +-
> Documentation/cgroups/blkio-controller.txt | 18 +++++++++---------
> Documentation/device-mapper/dm-raid.txt | 2 +-
> Documentation/device-mapper/persistent-data.txt | 2 +-
> .../devicetree/bindings/arm/omap/omap.txt | 2 +-
> Documentation/devicetree/bindings/arm/sirf.txt | 2 +-
> Documentation/devicetree/booting-without-of.txt | 2 +-
> Documentation/filesystems/ext4.txt | 4 ++--
> Documentation/filesystems/gfs2-uevents.txt | 2 +-
> Documentation/filesystems/vfs.txt | 2 +-
> Documentation/kbuild/kconfig-language.txt | 2 +-
> Documentation/security/Smack.txt | 2 +-
> Documentation/security/keys-trusted-encrypted.txt | 2 +-
> Documentation/security/keys.txt | 2 +-
> Documentation/virtual/kvm/mmu.txt | 4 ++--
> Documentation/vm/unevictable-lru.txt | 2 +-
> 17 files changed, 27 insertions(+), 27 deletions(-)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] [trivial] Documentation: Fix multiple typo in Documentation
2012-03-05 17:10 ` Randy Dunlap
@ 2012-03-06 16:08 ` Masanari Iida
0 siblings, 0 replies; 5+ messages in thread
From: Masanari Iida @ 2012-03-06 16:08 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-doc, linux-kernel, trivial
Randy,
Thanks for the correction.
I have fixed them up in my resend patch.
Masanari
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] [trivial] Documentation: Fix multiple typo in Documentation
2012-03-05 16:24 Masanari Iida
@ 2012-03-05 17:10 ` Randy Dunlap
2012-03-06 16:08 ` Masanari Iida
0 siblings, 1 reply; 5+ messages in thread
From: Randy Dunlap @ 2012-03-05 17:10 UTC (permalink / raw)
To: Masanari Iida; +Cc: linux-doc, linux-kernel, trivial
On 03/05/2012 08:24 AM, Masanari Iida wrote:
> Correct following typo within 25 files in Documentation.
>
> "explaination" to "explanation" in dmaengine.txt
> "fucntion" to "function" in static-keys.txt
> "useage" to "usage" in arm/kernel_user_helpers.txt
> "tranfer" to "transfer" in DocBook/libata.tmpl
> "devided" to "divided" in filesystems/qnx6.txt
> "appropriatly" to "appropriately" in i2o/ioctl
> "ususally" to "usually" in input/alps.txt
> "ocassionally" to "occasionally" in input/alps.txt
> "Ths" to "This" in scsi/ChangeLog.megaraid_sas
> "preceeded" to "preceded" in virtual/virtio-spec.txt
> "guarentees" to "guarantees" in virtual/virtio-spec.txt
> "withdrawl" to "withdrawal" in virtual/virtio-spec.txt
> "independantly" to "independently" in video4linux/uvcvideo.txt
> "Licenced" to "Licensed" in laptops/dslm.c
> "adress" to "address" in filesystems/qnx6.txt
> "Millenium" to "Millennium" in filesystems/qnx6.txt,
> fb/matrixfb.txt, howmon/adm1275, hwmon/max16064,
> hwmon/max34440, hwmon/max8688, hwmon/ucd9000, hwmon/ucd9200,
> hwmon/zl6100, scsi/tmscsim.txt, input/joystick.txt
> "endianess" to "endianness" in filesystems/qnx6.txt,
> ioctl/hdio.txt, networking/fore200e.txt,
> ide/ChangeLog.ide-cd.1994-2004
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
>
> ---
> Documentation/DocBook/libata.tmpl | 4 ++--
> Documentation/arm/kernel_user_helpers.txt | 2 +-
> Documentation/dmaengine.txt | 2 +-
> Documentation/fb/matroxfb.txt | 6 +++---
> Documentation/filesystems/qnx6.txt | 26 +++++++++++++-------------
> Documentation/hwmon/adm1275 | 2 +-
> Documentation/hwmon/max16064 | 4 ++--
> Documentation/hwmon/max34440 | 4 ++--
> Documentation/hwmon/max8688 | 4 ++--
> Documentation/hwmon/ucd9000 | 6 +++---
> Documentation/hwmon/ucd9200 | 8 ++++----
> Documentation/hwmon/zl6100 | 4 ++--
> Documentation/i2o/ioctl | 12 ++++++------
> Documentation/ide/ChangeLog.ide-cd.1994-2004 | 2 +-
> Documentation/input/alps.txt | 4 ++--
> Documentation/input/joystick.txt | 2 +-
> Documentation/ioctl/hdio.txt | 4 ++--
> Documentation/laptops/dslm.c | 2 +-
> Documentation/networking/fore200e.txt | 2 +-
> Documentation/scsi/ChangeLog.lpfc | 2 +-
> Documentation/scsi/ChangeLog.megaraid_sas | 2 +-
> Documentation/scsi/tmscsim.txt | 2 +-
> Documentation/static-keys.txt | 2 +-
> Documentation/video4linux/uvcvideo.txt | 2 +-
> Documentation/virtual/virtio-spec.txt | 8 ++++----
> 25 files changed, 59 insertions(+), 59 deletions(-)
> diff --git a/Documentation/fb/matroxfb.txt b/Documentation/fb/matroxfb.txt
> index e5ce8a1..a75cf19 100644
> --- a/Documentation/fb/matroxfb.txt
> +++ b/Documentation/fb/matroxfb.txt
> @@ -204,7 +204,7 @@ grayscale - enable grayscale summing. It works in PSEUDOCOLOR modes (text,
> can paint colors.
> nograyscale - disable grayscale summing. It is default.
> cross4MB - enables that pixel line can cross 4MB boundary. It is default for
> - non-Millenium.
> + non-Millennium.
> nocross4MB - pixel line must not cross 4MB boundary. It is default for
> Millenium I or II, because of these devices have hardware
Millennium
> limitations which do not allow this. But this option is
> diff --git a/Documentation/filesystems/qnx6.txt b/Documentation/filesystems/qnx6.txt
> index 050223e..1a2e929 100644
> --- a/Documentation/filesystems/qnx6.txt
> +++ b/Documentation/filesystems/qnx6.txt
> @@ -47,16 +47,16 @@ inactive superblock.
> Each superblock holds a set of root inodes for the different filesystem
> parts. (Inode, Bitmap and Longfilenames)
> Each of these root nodes holds information like total size of the stored
> -data and the adressing levels in that specific tree.
> -If the level value is 0, up to 16 direct blocks can be adressed by each
> +data and the addressing levels in that specific tree.
> +If the level value is 0, up to 16 direct blocks can be addressed by each
> node.
> -Level 1 adds an additional indirect adressing level where each indirect
> -adressing block holds up to blocksize / 4 bytes pointers to data blocks.
> -Level 2 adds an additional indirect adressig block level (so, already up
> -to 16 * 256 * 256 = 1048576 blocks that can be adressed by such a tree)a
> +Level 1 adds an additional indirect addressing level where each indirect
> +addressing block holds up to blocksize / 4 bytes pointers to data blocks.
> +Level 2 adds an additional indirect addressig block level (so, already up
addressing
> +to 16 * 256 * 256 = 1048576 blocks that can be addressed by such a tree)a
>
> @@ -148,7 +148,7 @@ smaller than addressing space in the bitmap.
> Bitmap system area
> ------------------
>
> -The bitmap itself is devided into three parts.
> +The bitmap itself is divided into three parts.
> First the system area, that is split into two halfs.
halves.
> Then userspace.
>
> diff --git a/Documentation/ide/ChangeLog.ide-cd.1994-2004 b/Documentation/ide/ChangeLog.ide-cd.1994-2004
> index 190d17b..b2cf804 100644
> --- a/Documentation/ide/ChangeLog.ide-cd.1994-2004
> +++ b/Documentation/ide/ChangeLog.ide-cd.1994-2004
> @@ -175,7 +175,7 @@
> * since the .pdf version doesn't seem to work...
> * -- Updated the TODO list to something more current.
> *
> - * 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect mechine endianess,
> + * 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect mechine endianness,
machine
> * patch thanks to "Eddie C. Dost" <ecd@skynet.be>
> *
> * 4.50 Oct 19, 1998 -- New maintainers!
> diff --git a/Documentation/input/joystick.txt b/Documentation/input/joystick.txt
> index 8007b7c..87ac40c 100644
> --- a/Documentation/input/joystick.txt
> +++ b/Documentation/input/joystick.txt
> @@ -330,7 +330,7 @@ the USB documentation for how to setup an USB mouse.
> The TM DirectConnect (BSP) protocol is supported by the tmdc.c
> module. This includes, but is not limited to:
>
> -* ThrustMaster Millenium 3D Inceptor
> +* ThrustMaster Millennium 3D Inceptor
Interceptor
> * ThrustMaster 3D Rage Pad
> * ThrustMaster Fusion Digital Game Pad
>
> diff --git a/Documentation/laptops/dslm.c b/Documentation/laptops/dslm.c
> index 72ff290..d5dd2d4 100644
> --- a/Documentation/laptops/dslm.c
> +++ b/Documentation/laptops/dslm.c
> @@ -2,7 +2,7 @@
> * dslm.c
> * Simple Disk Sleep Monitor
> * by Bartek Kania
> - * Licenced under the GPL
above is OK.
> + * Licensed under the GPL
> */
> #include <unistd.h>
> #include <stdlib.h>
Thanks.
---
~Randy
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH] [trivial] Documentation: Fix multiple typo in Documentation
@ 2012-03-05 16:24 Masanari Iida
2012-03-05 17:10 ` Randy Dunlap
0 siblings, 1 reply; 5+ messages in thread
From: Masanari Iida @ 2012-03-05 16:24 UTC (permalink / raw)
To: rdunlap, linux-doc; +Cc: linux-kernel, trivial, Masanari Iida
Correct following typo within 25 files in Documentation.
"explaination" to "explanation" in dmaengine.txt
"fucntion" to "function" in static-keys.txt
"useage" to "usage" in arm/kernel_user_helpers.txt
"tranfer" to "transfer" in DocBook/libata.tmpl
"devided" to "divided" in filesystems/qnx6.txt
"appropriatly" to "appropriately" in i2o/ioctl
"ususally" to "usually" in input/alps.txt
"ocassionally" to "occasionally" in input/alps.txt
"Ths" to "This" in scsi/ChangeLog.megaraid_sas
"preceeded" to "preceded" in virtual/virtio-spec.txt
"guarentees" to "guarantees" in virtual/virtio-spec.txt
"withdrawl" to "withdrawal" in virtual/virtio-spec.txt
"independantly" to "independently" in video4linux/uvcvideo.txt
"Licenced" to "Licensed" in laptops/dslm.c
"adress" to "address" in filesystems/qnx6.txt
"Millenium" to "Millennium" in filesystems/qnx6.txt,
fb/matrixfb.txt, howmon/adm1275, hwmon/max16064,
hwmon/max34440, hwmon/max8688, hwmon/ucd9000, hwmon/ucd9200,
hwmon/zl6100, scsi/tmscsim.txt, input/joystick.txt
"endianess" to "endianness" in filesystems/qnx6.txt,
ioctl/hdio.txt, networking/fore200e.txt,
ide/ChangeLog.ide-cd.1994-2004
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
---
Documentation/DocBook/libata.tmpl | 4 ++--
Documentation/arm/kernel_user_helpers.txt | 2 +-
Documentation/dmaengine.txt | 2 +-
Documentation/fb/matroxfb.txt | 6 +++---
Documentation/filesystems/qnx6.txt | 26 +++++++++++++-------------
Documentation/hwmon/adm1275 | 2 +-
Documentation/hwmon/max16064 | 4 ++--
Documentation/hwmon/max34440 | 4 ++--
Documentation/hwmon/max8688 | 4 ++--
Documentation/hwmon/ucd9000 | 6 +++---
Documentation/hwmon/ucd9200 | 8 ++++----
Documentation/hwmon/zl6100 | 4 ++--
Documentation/i2o/ioctl | 12 ++++++------
Documentation/ide/ChangeLog.ide-cd.1994-2004 | 2 +-
Documentation/input/alps.txt | 4 ++--
Documentation/input/joystick.txt | 2 +-
Documentation/ioctl/hdio.txt | 4 ++--
Documentation/laptops/dslm.c | 2 +-
Documentation/networking/fore200e.txt | 2 +-
Documentation/scsi/ChangeLog.lpfc | 2 +-
Documentation/scsi/ChangeLog.megaraid_sas | 2 +-
Documentation/scsi/tmscsim.txt | 2 +-
Documentation/static-keys.txt | 2 +-
Documentation/video4linux/uvcvideo.txt | 2 +-
Documentation/virtual/virtio-spec.txt | 8 ++++----
25 files changed, 59 insertions(+), 59 deletions(-)
diff --git a/Documentation/DocBook/libata.tmpl b/Documentation/DocBook/libata.tmpl
index 880c956..31df1aa 100644
--- a/Documentation/DocBook/libata.tmpl
+++ b/Documentation/DocBook/libata.tmpl
@@ -945,7 +945,7 @@ and other resources, etc.
<listitem>
<para>
- !BSY && ERR after CDB tranfer starts but before the
+ !BSY && ERR after CDB transfer starts but before the
last byte of CDB is transferred. ATA/ATAPI standard states
that "The device shall not terminate the PACKET command
with an error before the last byte of the command packet has
@@ -1050,7 +1050,7 @@ and other resources, etc.
to complete a command. Combined with the fact that MWDMA
and PIO transfer errors aren't allowed to use ICRC bit up to
ATA/ATAPI-7, it seems to imply that ABRT bit alone could
- indicate tranfer errors.
+ indicate transfer errors.
</para>
<para>
However, ATA/ATAPI-8 draft revision 1f removes the part
diff --git a/Documentation/arm/kernel_user_helpers.txt b/Documentation/arm/kernel_user_helpers.txt
index a17df9f..5673594 100644
--- a/Documentation/arm/kernel_user_helpers.txt
+++ b/Documentation/arm/kernel_user_helpers.txt
@@ -25,7 +25,7 @@ inline (either in the code emitted directly by the compiler, or part of
the implementation of a library call) when optimizing for a recent enough
processor that has the necessary native support, but only if resulting
binaries are already to be incompatible with earlier ARM processors due to
-useage of similar native instructions for other things. In other words
+usage of similar native instructions for other things. In other words
don't make binaries unable to run on earlier processors just for the sake
of not using these kernel helpers if your compiled code is not going to
use new instructions for other purpose.
diff --git a/Documentation/dmaengine.txt b/Documentation/dmaengine.txt
index bbe6cb3..879b6e3 100644
--- a/Documentation/dmaengine.txt
+++ b/Documentation/dmaengine.txt
@@ -63,7 +63,7 @@ The slave DMA usage consists of following steps:
struct dma_slave_config *config)
Please see the dma_slave_config structure definition in dmaengine.h
- for a detailed explaination of the struct members. Please note
+ for a detailed explanation of the struct members. Please note
that the 'direction' member will be going away as it duplicates the
direction given in the prepare call.
diff --git a/Documentation/fb/matroxfb.txt b/Documentation/fb/matroxfb.txt
index e5ce8a1..a75cf19 100644
--- a/Documentation/fb/matroxfb.txt
+++ b/Documentation/fb/matroxfb.txt
@@ -177,8 +177,8 @@ sgram - tells to driver that you have Gxx0 with SGRAM memory. It has no
effect without `init'.
sdram - tells to driver that you have Gxx0 with SDRAM memory.
It is a default.
-inv24 - change timings parameters for 24bpp modes on Millenium and
- Millenium II. Specify this if you see strange color shadows around
+inv24 - change timings parameters for 24bpp modes on Millennium and
+ Millennium II. Specify this if you see strange color shadows around
characters.
noinv24 - use standard timings. It is the default.
inverse - invert colors on screen (for LCD displays)
@@ -204,7 +204,7 @@ grayscale - enable grayscale summing. It works in PSEUDOCOLOR modes (text,
can paint colors.
nograyscale - disable grayscale summing. It is default.
cross4MB - enables that pixel line can cross 4MB boundary. It is default for
- non-Millenium.
+ non-Millennium.
nocross4MB - pixel line must not cross 4MB boundary. It is default for
Millenium I or II, because of these devices have hardware
limitations which do not allow this. But this option is
diff --git a/Documentation/filesystems/qnx6.txt b/Documentation/filesystems/qnx6.txt
index 050223e..1a2e929 100644
--- a/Documentation/filesystems/qnx6.txt
+++ b/Documentation/filesystems/qnx6.txt
@@ -17,7 +17,7 @@ concepts of blocks, inodes and directories.
On QNX it is possible to create little endian and big endian qnx6 filesystems.
This feature makes it possible to create and use a different endianness fs
for the target (QNX is used on quite a range of embedded systems) plattform
-running on a different endianess.
+running on a different endianness.
The Linux driver handles endianness transparently. (LE and BE)
Blocks
@@ -26,7 +26,7 @@ Blocks
The space in the device or file is split up into blocks. These are a fixed
size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
created.
-Blockpointers are 32bit, so the maximum space that can be adressed is
+Blockpointers are 32bit, so the maximum space that can be addressed is
2^32 * 4096 bytes or 16TB
The superblocks
@@ -47,16 +47,16 @@ inactive superblock.
Each superblock holds a set of root inodes for the different filesystem
parts. (Inode, Bitmap and Longfilenames)
Each of these root nodes holds information like total size of the stored
-data and the adressing levels in that specific tree.
-If the level value is 0, up to 16 direct blocks can be adressed by each
+data and the addressing levels in that specific tree.
+If the level value is 0, up to 16 direct blocks can be addressed by each
node.
-Level 1 adds an additional indirect adressing level where each indirect
-adressing block holds up to blocksize / 4 bytes pointers to data blocks.
-Level 2 adds an additional indirect adressig block level (so, already up
-to 16 * 256 * 256 = 1048576 blocks that can be adressed by such a tree)a
+Level 1 adds an additional indirect addressing level where each indirect
+addressing block holds up to blocksize / 4 bytes pointers to data blocks.
+Level 2 adds an additional indirect addressig block level (so, already up
+to 16 * 256 * 256 = 1048576 blocks that can be addressed by such a tree)a
Unused block pointers are always set to ~0 - regardless of root node,
-indirect adressing blocks or inodes.
+indirect addressing blocks or inodes.
Data leaves are always on the lowest level. So no data is stored on upper
tree levels.
@@ -83,8 +83,8 @@ size, number of blocks used, access time, change time and modification time.
Object mode field is POSIX format. (which makes things easier)
There are also pointers to the first 16 blocks, if the object data can be
-adressed with 16 direct blocks.
-For more than 16 blocks an indirect adressing in form of another tree is
+addressed with 16 direct blocks.
+For more than 16 blocks an indirect addressing in form of another tree is
used. (scheme is the same as the one used for the superblock root nodes)
The filesize is stored 64bit. Inode counting starts with 1. (whilst long
@@ -124,7 +124,7 @@ underlaying filesystem.
Long filenames
--------------
-Long filenames are stored in a seperate adressing tree. The staring point
+Long filenames are stored in a separate addressing tree. The staring point
is the longfilename root node in the active superblock.
Each data block (tree leaves) holds one long filename. That filename is
limited to 510 bytes. The first two starting bytes are used as length field
@@ -148,7 +148,7 @@ smaller than addressing space in the bitmap.
Bitmap system area
------------------
-The bitmap itself is devided into three parts.
+The bitmap itself is divided into three parts.
First the system area, that is split into two halfs.
Then userspace.
diff --git a/Documentation/hwmon/adm1275 b/Documentation/hwmon/adm1275
index ab70d96..e5f982c 100644
--- a/Documentation/hwmon/adm1275
+++ b/Documentation/hwmon/adm1275
@@ -53,7 +53,7 @@ attributes are write-only, all other attributes are read-only.
in1_label "vin1" or "vout1" depending on chip variant and
configuration.
in1_input Measured voltage.
-in1_min Minumum Voltage.
+in1_min Minimum Voltage.
in1_max Maximum voltage.
in1_min_alarm Voltage low alarm.
in1_max_alarm Voltage high alarm.
diff --git a/Documentation/hwmon/max16064 b/Documentation/hwmon/max16064
index f6e8bcb..f8b4780 100644
--- a/Documentation/hwmon/max16064
+++ b/Documentation/hwmon/max16064
@@ -42,9 +42,9 @@ attributes are read-only.
in[1-4]_label "vout[1-4]"
in[1-4]_input Measured voltage. From READ_VOUT register.
-in[1-4]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register.
+in[1-4]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-4]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
-in[1-4]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register.
+in[1-4]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-4]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
diff --git a/Documentation/hwmon/max34440 b/Documentation/hwmon/max34440
index 36b335c..ebc2971 100644
--- a/Documentation/hwmon/max34440
+++ b/Documentation/hwmon/max34440
@@ -48,9 +48,9 @@ attributes are read-only.
in[1-6]_label "vout[1-6]".
in[1-6]_input Measured voltage. From READ_VOUT register.
-in[1-6]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register.
+in[1-6]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-6]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
-in[1-6]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register.
+in[1-6]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-6]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-6]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-6]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
diff --git a/Documentation/hwmon/max8688 b/Documentation/hwmon/max8688
index 71ed10a..fe84987 100644
--- a/Documentation/hwmon/max8688
+++ b/Documentation/hwmon/max8688
@@ -42,9 +42,9 @@ attributes are read-only.
in1_label "vout1"
in1_input Measured voltage. From READ_VOUT register.
-in1_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register.
+in1_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in1_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
-in1_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register.
+in1_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in1_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in1_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in1_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
diff --git a/Documentation/hwmon/ucd9000 b/Documentation/hwmon/ucd9000
index 40ca6db..0df5f27 100644
--- a/Documentation/hwmon/ucd9000
+++ b/Documentation/hwmon/ucd9000
@@ -70,9 +70,9 @@ attributes are read-only.
in[1-12]_label "vout[1-12]".
in[1-12]_input Measured voltage. From READ_VOUT register.
-in[1-12]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register.
+in[1-12]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-12]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
-in[1-12]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register.
+in[1-12]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-12]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-12]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-12]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
@@ -82,7 +82,7 @@ in[1-12]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
curr[1-12]_label "iout[1-12]".
curr[1-12]_input Measured current. From READ_IOUT register.
curr[1-12]_max Maximum current. From IOUT_OC_WARN_LIMIT register.
-curr[1-12]_lcrit Critical minumum output current. From IOUT_UC_FAULT_LIMIT
+curr[1-12]_lcrit Critical minimum output current. From IOUT_UC_FAULT_LIMIT
register.
curr[1-12]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register.
curr[1-12]_max_alarm Current high alarm. From IOUT_OC_WARNING status.
diff --git a/Documentation/hwmon/ucd9200 b/Documentation/hwmon/ucd9200
index 3c58607..1abb179 100644
--- a/Documentation/hwmon/ucd9200
+++ b/Documentation/hwmon/ucd9200
@@ -54,9 +54,9 @@ attributes are read-only.
in1_label "vin".
in1_input Measured voltage. From READ_VIN register.
-in1_min Minumum Voltage. From VIN_UV_WARN_LIMIT register.
+in1_min Minimum Voltage. From VIN_UV_WARN_LIMIT register.
in1_max Maximum voltage. From VIN_OV_WARN_LIMIT register.
-in1_lcrit Critical minumum Voltage. VIN_UV_FAULT_LIMIT register.
+in1_lcrit Critical minimum Voltage. VIN_UV_FAULT_LIMIT register.
in1_crit Critical maximum voltage. From VIN_OV_FAULT_LIMIT register.
in1_min_alarm Voltage low alarm. From VIN_UV_WARNING status.
in1_max_alarm Voltage high alarm. From VIN_OV_WARNING status.
@@ -67,7 +67,7 @@ in[2-5]_label "vout[1-4]".
in[2-5]_input Measured voltage. From READ_VOUT register.
in[2-5]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register.
in[2-5]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
-in[2-5]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register.
+in[2-5]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[2-5]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[2-5]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[2-5]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
@@ -80,7 +80,7 @@ curr1_input Measured current. From READ_IIN register.
curr[2-5]_label "iout[1-4]".
curr[2-5]_input Measured current. From READ_IOUT register.
curr[2-5]_max Maximum current. From IOUT_OC_WARN_LIMIT register.
-curr[2-5]_lcrit Critical minumum output current. From IOUT_UC_FAULT_LIMIT
+curr[2-5]_lcrit Critical minimum output current. From IOUT_UC_FAULT_LIMIT
register.
curr[2-5]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register.
curr[2-5]_max_alarm Current high alarm. From IOUT_OC_WARNING status.
diff --git a/Documentation/hwmon/zl6100 b/Documentation/hwmon/zl6100
index 51f76a1..5865a24 100644
--- a/Documentation/hwmon/zl6100
+++ b/Documentation/hwmon/zl6100
@@ -108,7 +108,7 @@ in1_label "vin"
in1_input Measured input voltage.
in1_min Minimum input voltage.
in1_max Maximum input voltage.
-in1_lcrit Critical minumum input voltage.
+in1_lcrit Critical minimum input voltage.
in1_crit Critical maximum input voltage.
in1_min_alarm Input voltage low alarm.
in1_max_alarm Input voltage high alarm.
@@ -117,7 +117,7 @@ in1_crit_alarm Input voltage critical high alarm.
in2_label "vout1"
in2_input Measured output voltage.
-in2_lcrit Critical minumum output Voltage.
+in2_lcrit Critical minimum output Voltage.
in2_crit Critical maximum output voltage.
in2_lcrit_alarm Critical output voltage critical low alarm.
in2_crit_alarm Critical output voltage critical high alarm.
diff --git a/Documentation/i2o/ioctl b/Documentation/i2o/ioctl
index 22ca53a..27c3c54 100644
--- a/Documentation/i2o/ioctl
+++ b/Documentation/i2o/ioctl
@@ -138,7 +138,7 @@ VI. Setting Parameters
The return value is the size in bytes of the data written into
ops->resbuf if no errors occur. If an error occurs, -1 is returned
- and errno is set appropriatly:
+ and errno is set appropriately:
EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number
@@ -222,7 +222,7 @@ VIII. Downloading Software
RETURNS
This function returns 0 no errors occur. If an error occurs, -1
- is returned and errno is set appropriatly:
+ is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number
@@ -264,7 +264,7 @@ IX. Uploading Software
RETURNS
This function returns 0 if no errors occur. If an error occurs, -1
- is returned and errno is set appropriatly:
+ is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number
@@ -301,7 +301,7 @@ X. Removing Software
RETURNS
This function returns 0 if no errors occur. If an error occurs, -1
- is returned and errno is set appropriatly:
+ is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number
@@ -325,7 +325,7 @@ X. Validating Configuration
RETURNS
This function returns 0 if no erro occur. If an error occurs, -1 is
- returned and errno is set appropriatly:
+ returned and errno is set appropriately:
ETIMEDOUT Timeout waiting for reply message
ENXIO Invalid IOP number
@@ -360,7 +360,7 @@ XI. Configuration Dialog
RETURNS
This function returns 0 if no error occur. If an error occurs, -1
- is returned and errno is set appropriatly:
+ is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number
diff --git a/Documentation/ide/ChangeLog.ide-cd.1994-2004 b/Documentation/ide/ChangeLog.ide-cd.1994-2004
index 190d17b..b2cf804 100644
--- a/Documentation/ide/ChangeLog.ide-cd.1994-2004
+++ b/Documentation/ide/ChangeLog.ide-cd.1994-2004
@@ -175,7 +175,7 @@
* since the .pdf version doesn't seem to work...
* -- Updated the TODO list to something more current.
*
- * 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect mechine endianess,
+ * 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect mechine endianness,
* patch thanks to "Eddie C. Dost" <ecd@skynet.be>
*
* 4.50 Oct 19, 1998 -- New maintainers!
diff --git a/Documentation/input/alps.txt b/Documentation/input/alps.txt
index 2f95308..c7c5d33 100644
--- a/Documentation/input/alps.txt
+++ b/Documentation/input/alps.txt
@@ -132,8 +132,8 @@ number of contacts (f1 and f0 in the table below).
byte 5: 0 1 ? ? ? ? f1 f0
This packet only appears after a position packet with the mt bit set, and
-ususally only appears when there are two or more contacts (although
-ocassionally it's seen with only a single contact).
+usually only appears when there are two or more contacts (although
+occasionally it's seen with only a single contact).
The final v3 packet type is the trackstick packet.
diff --git a/Documentation/input/joystick.txt b/Documentation/input/joystick.txt
index 8007b7c..87ac40c 100644
--- a/Documentation/input/joystick.txt
+++ b/Documentation/input/joystick.txt
@@ -330,7 +330,7 @@ the USB documentation for how to setup an USB mouse.
The TM DirectConnect (BSP) protocol is supported by the tmdc.c
module. This includes, but is not limited to:
-* ThrustMaster Millenium 3D Inceptor
+* ThrustMaster Millennium 3D Inceptor
* ThrustMaster 3D Rage Pad
* ThrustMaster Fusion Digital Game Pad
diff --git a/Documentation/ioctl/hdio.txt b/Documentation/ioctl/hdio.txt
index 91a6ecb..18eb98c 100644
--- a/Documentation/ioctl/hdio.txt
+++ b/Documentation/ioctl/hdio.txt
@@ -596,7 +596,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile
if CHS/LBA28
The association between in_flags.all and each enable
- bitfield flips depending on endianess; fortunately, TASKFILE
+ bitfield flips depending on endianness; fortunately, TASKFILE
only uses inflags.b.data bit and ignores all other bits.
The end result is that, on any endian machines, it has no
effect other than modifying in_flags on completion.
@@ -720,7 +720,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile
[6] Do not access {in|out}_flags->all except for resetting
all the bits. Always access individual bit fields. ->all
- value will flip depending on endianess. For the same
+ value will flip depending on endianness. For the same
reason, do not use IDE_{TASKFILE|HOB}_STD_{OUT|IN}_FLAGS
constants defined in hdreg.h.
diff --git a/Documentation/laptops/dslm.c b/Documentation/laptops/dslm.c
index 72ff290..d5dd2d4 100644
--- a/Documentation/laptops/dslm.c
+++ b/Documentation/laptops/dslm.c
@@ -2,7 +2,7 @@
* dslm.c
* Simple Disk Sleep Monitor
* by Bartek Kania
- * Licenced under the GPL
+ * Licensed under the GPL
*/
#include <unistd.h>
#include <stdlib.h>
diff --git a/Documentation/networking/fore200e.txt b/Documentation/networking/fore200e.txt
index 6e0d2a9..f648eb2 100644
--- a/Documentation/networking/fore200e.txt
+++ b/Documentation/networking/fore200e.txt
@@ -44,7 +44,7 @@ the 'software updates' pages. The firmware binaries are part of
the various ForeThought software distributions.
Notice that different versions of the PCA-200E firmware exist, depending
-on the endianess of the host architecture. The driver is shipped with
+on the endianness of the host architecture. The driver is shipped with
both little and big endian PCA firmware images.
Name and location of the new firmware images can be set at kernel
diff --git a/Documentation/scsi/ChangeLog.lpfc b/Documentation/scsi/ChangeLog.lpfc
index c56ec99..2f6d595 100644
--- a/Documentation/scsi/ChangeLog.lpfc
+++ b/Documentation/scsi/ChangeLog.lpfc
@@ -1718,7 +1718,7 @@ Changes from 20040319 to 20040326
* lpfc_els_timeout_handler() now uses system timer.
* Further cleanup of #ifdef powerpc
* lpfc_scsi_timeout_handler() now uses system timer.
- * Replace common driver's own defines for endianess w/ Linux's
+ * Replace common driver's own defines for endianness w/ Linux's
__BIG_ENDIAN etc.
* Added #ifdef IPFC for all IPFC specific code.
* lpfc_disc_retry_rptlun() now uses system timer.
diff --git a/Documentation/scsi/ChangeLog.megaraid_sas b/Documentation/scsi/ChangeLog.megaraid_sas
index 57566ba..83f8ea8 100644
--- a/Documentation/scsi/ChangeLog.megaraid_sas
+++ b/Documentation/scsi/ChangeLog.megaraid_sas
@@ -510,7 +510,7 @@ i. Support for 1078 type (ppc IOP) controller, device id : 0x60 added.
3 Older Version : 00.00.02.02
i. Register 16 byte CDB capability with scsi midlayer
- "Ths patch properly registers the 16 byte command length capability of the
+ "This patch properly registers the 16 byte command length capability of the
megaraid_sas controlled hardware with the scsi midlayer. All megaraid_sas
hardware supports 16 byte CDB's."
diff --git a/Documentation/scsi/tmscsim.txt b/Documentation/scsi/tmscsim.txt
index 61c0531..3303d21 100644
--- a/Documentation/scsi/tmscsim.txt
+++ b/Documentation/scsi/tmscsim.txt
@@ -102,7 +102,7 @@ So take at least the following measures:
ftp://student.physik.uni-dortmund.de/pub/linux/kernel/bootdisk.gz
One more warning: I used to overclock my PCI bus to 41.67 MHz. My Tekram
-DC390F (Sym53c875) accepted this as well as my Millenium. But the Am53C974
+DC390F (Sym53c875) accepted this as well as my Millennium. But the Am53C974
produced errors and started to corrupt my disks. So don't do that! A 37.50
MHz PCI bus works for me, though, but I don't recommend using higher clocks
than the 33.33 MHz being in the PCI spec.
diff --git a/Documentation/static-keys.txt b/Documentation/static-keys.txt
index d93f3c0..9f5263d 100644
--- a/Documentation/static-keys.txt
+++ b/Documentation/static-keys.txt
@@ -235,7 +235,7 @@ label case adds:
6 (mov) + 2 (test) + 2 (jne) = 10 - 5 (5 byte jump 0) = 5 addition bytes.
If we then include the padding bytes, the jump label code saves, 16 total bytes
-of instruction memory for this small fucntion. In this case the non-jump label
+of instruction memory for this small function. In this case the non-jump label
function is 80 bytes long. Thus, we have have saved 20% of the instruction
footprint. We can in fact improve this even further, since the 5-byte no-op
really can be a 2-byte no-op since we can reach the branch with a 2-byte jmp.
diff --git a/Documentation/video4linux/uvcvideo.txt b/Documentation/video4linux/uvcvideo.txt
index 848d620..35ce19c 100644
--- a/Documentation/video4linux/uvcvideo.txt
+++ b/Documentation/video4linux/uvcvideo.txt
@@ -116,7 +116,7 @@ Description:
A UVC control can be mapped to several V4L2 controls. For instance,
a UVC pan/tilt control could be mapped to separate pan and tilt V4L2
controls. The UVC control is divided into non overlapping fields using
- the 'size' and 'offset' fields and are then independantly mapped to
+ the 'size' and 'offset' fields and are then independently mapped to
V4L2 control.
For signed integer V4L2 controls the data_type field should be set to
diff --git a/Documentation/virtual/virtio-spec.txt b/Documentation/virtual/virtio-spec.txt
index 401ffd0..289cf77 100644
--- a/Documentation/virtual/virtio-spec.txt
+++ b/Documentation/virtual/virtio-spec.txt
@@ -1387,7 +1387,7 @@ segmentation, if both guests are amenable.
Packets are transmitted by placing them in the transmitq, and
buffers for incoming packets are placed in the receiveq. In each
-case, the packet itself is preceeded by a header:
+case, the packet itself is preceded by a header:
struct virtio_net_hdr {
@@ -1629,7 +1629,7 @@ struct virtio_net_ctrl_mac {
The device can filter incoming packets by any number of
destination MAC addresses.[footnote:
-Since there are no guarentees, it can use a hash filter
+Since there are no guarantees, it can use a hash filter
orsilently switch to allmulti or promiscuous mode if it is given
too many addresses.
] This table is set using the class VIRTIO_NET_CTRL_MAC and the
@@ -1806,7 +1806,7 @@ the FLUSH and FLUSH_OUT types are equivalent, the device does not
distinguish between them
]). If the device has VIRTIO_BLK_F_BARRIER feature the high bit
(VIRTIO_BLK_T_BARRIER) indicates that this request acts as a
-barrier and that all preceeding requests must be complete before
+barrier and that all preceding requests must be complete before
this one, and all following requests must not be started until
this is complete. Note that a barrier does not flush caches in
the underlying backend device in host, and thus does not serve as
@@ -2119,7 +2119,7 @@ This is historical, and independent of the guest page size
Otherwise, the guest may begin to re-use pages previously given
to the balloon before the device has acknowledged their
- withdrawl. [footnote:
+ withdrawal. [footnote:
In this case, deflation advice is merely a courtesy
]
--
1.7.9.2.262.gba998
^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-03-06 16:08 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-03-04 14:16 [PATCH] [trivial] Documentation: Fix multiple typo in Documentation Masanari Iida
2012-03-04 17:06 ` Randy Dunlap
2012-03-05 16:24 Masanari Iida
2012-03-05 17:10 ` Randy Dunlap
2012-03-06 16:08 ` Masanari Iida
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).