[PATCH 00/41] Documentation: fix spelling mistakes

classic Classic list List threaded Threaded
93 messages Options
12345
Reply | Threaded
Open this post in threaded view
|

[PATCH 20/41] Documentation: dt: pinctrl: fix spelling mistake

Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt b/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
index a90c812..a54c39e 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
@@ -122,7 +122,7 @@ to specify in a pin configuration subnode:
     2: 1.5uA                    (PMIC_GPIO_PULL_UP_1P5)
     3: 31.5uA                   (PMIC_GPIO_PULL_UP_31P5)
     4: 1.5uA + 30uA boost       (PMIC_GPIO_PULL_UP_1P5_30)
-    If this property is ommited 30uA strength will be used if
+    If this property is omitted 30uA strength will be used if
     pull up is selected
 
 - bias-high-impedance:
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 21/41] Documentation: dt: power: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/devicetree/bindings/power/qcom,coincell-charger.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/power/qcom,coincell-charger.txt b/Documentation/devicetree/bindings/power/qcom,coincell-charger.txt
index 0e6d875..7478992 100644
--- a/Documentation/devicetree/bindings/power/qcom,coincell-charger.txt
+++ b/Documentation/devicetree/bindings/power/qcom,coincell-charger.txt
@@ -29,7 +29,7 @@ IC (PMIC)
 - qcom,charger-disable:
  Usage: optional
  Value type: <boolean>
- Definition: definining this property disables charging
+ Definition: defining this property disables charging
 
 This charger is a sub-node of one of the 8941 PMIC blocks, and is specified
 as a child node in DTS of that node.  See ../mfd/qcom,spmi-pmic.txt and
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 22/41] Documentation: dt: soc: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 .../devicetree/bindings/soc/ti/keystone-navigator-qmss.txt          | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt b/Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
index d1ce21a..64c66a5 100644
--- a/Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
+++ b/Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
@@ -42,7 +42,7 @@ Required properties:
 - queue-pools : child node classifying the queue ranges into pools.
   Queue ranges are grouped into 3 type of pools:
   - qpend    : pool of qpend(interruptible) queues
-  - general-purpose : pool of general queues, primarly used
+  - general-purpose : pool of general queues, primarily used
       as free descriptor queues or the
       transmit DMA queues.
   - accumulator    : pool of queues on PDSP accumulator channel
@@ -50,7 +50,7 @@ Required properties:
   -- qrange : number of queues to use per queue range, specified as
   <"base queue #" "# of queues">.
   -- interrupts : Optional property to specify the interrupt mapping
-  for interruptible queues. The driver additionaly sets
+  for interruptible queues. The driver additionally sets
   the interrupt affinity hint based on the cpu mask.
   -- qalloc-by-id : Optional property to specify that the queues in this
   range can only be allocated by queue id.
@@ -80,7 +80,7 @@ Required properties:
   latency     : time to delay the interrupt, specified
  in microseconds.
   -- multi-queue : Optional property to specify that the channel has to
-  monitor upto 32 queues starting at the base queue #.
+  monitor up to 32 queues starting at the base queue #.
 - descriptor-regions : child node describing the memory regions for keystone
   navigator packet DMA descriptors. The memory for
   descriptors will be allocated by the driver.
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 24/41] Documentation: fb: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/fb/udlfb.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/fb/udlfb.txt b/Documentation/fb/udlfb.txt
index 57d2f29..c985cb6 100644
--- a/Documentation/fb/udlfb.txt
+++ b/Documentation/fb/udlfb.txt
@@ -9,7 +9,7 @@ pairing that with a hardware framebuffer (16MB) on the other end of the
 USB wire.  That hardware framebuffer is able to drive the VGA, DVI, or HDMI
 monitor with no CPU involvement until a pixel has to change.
 
-The CPU or other local resource does all the rendering; optinally compares the
+The CPU or other local resource does all the rendering; optionally compares the
 result with a local shadow of the remote hardware framebuffer to identify
 the minimal set of pixels that have changed; and compresses and sends those
 pixels line-by-line via USB bulk transfers.
@@ -66,10 +66,10 @@ means that from a hardware and fbdev software perspective, everything is good.
 At that point, a /dev/fb? interface will be present for user-mode applications
 to open and begin writing to the framebuffer of the DisplayLink device using
 standard fbdev calls.  Note that if mmap() is used, by default the user mode
-application must send down damage notifcations to trigger repaints of the
+application must send down damage notifications to trigger repaints of the
 changed regions.  Alternatively, udlfb can be recompiled with experimental
 defio support enabled, to support a page-fault based detection mechanism
-that can work without explicit notifcation.
+that can work without explicit notification.
 
 The most common client of udlfb is xf86-video-displaylink or a modified
 xf86-video-fbdev X server. These servers have no real DisplayLink specific
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 25/41] Documentation: filesystems: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/filesystems/autofs4.txt  | 6 +++---
 Documentation/filesystems/cifs/CHANGES | 2 +-
 Documentation/filesystems/proc.txt     | 4 ++--
 Documentation/filesystems/vfs.txt      | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/filesystems/autofs4.txt b/Documentation/filesystems/autofs4.txt
index 39d02e1..25fe9db 100644
--- a/Documentation/filesystems/autofs4.txt
+++ b/Documentation/filesystems/autofs4.txt
@@ -225,7 +225,7 @@ unmount any filesystems mounted on the autofs filesystem or remove any
 symbolic links or empty directories any time it likes.  If the unmount
 or removal is successful the filesystem will be returned to the state
 it was before the mount or creation, so that any access of the name
-will trigger normal auto-mount processing.  In particlar, `rmdir` and
+will trigger normal auto-mount processing.  In particular, `rmdir` and
 `unlink` do not leave negative entries in the dcache as a normal
 filesystem would, so an attempt to access a recently-removed object is
 passed to autofs for handling.
@@ -242,7 +242,7 @@ time stamp on each directory or symlink.  For symlinks it genuinely
 does record the last time the symlink was "used" or followed to find
 out where it points to.  For directories the field is a slight
 misnomer.  It actually records the last time that autofs checked if
-the directory or one of its descendents was busy and found that it
+the directory or one of its descendants was busy and found that it
 was.  This is just as useful and doesn't require updating the field so
 often.
 
@@ -255,7 +255,7 @@ up.
 
 There is an option with indirect mounts to consider each of the leaves
 that has been mounted on instead of considering the top-level names.
-This is intended for compatability with version 4 of autofs and should
+This is intended for compatibility with version 4 of autofs and should
 be considered as deprecated.
 
 When autofs considers a directory it checks the `last_used` time and
diff --git a/Documentation/filesystems/cifs/CHANGES b/Documentation/filesystems/cifs/CHANGES
index bc0025c..fe8f1ed 100644
--- a/Documentation/filesystems/cifs/CHANGES
+++ b/Documentation/filesystems/cifs/CHANGES
@@ -455,7 +455,7 @@ Fix internationalization problem in cifs readdir with filenames that map to
 longer UTF-8 strings than the string on the wire was in Unicode.  Add workaround
 for readdir to netapp servers. Fix search rewind (seek into readdir to return
 non-consecutive entries).  Do not do readdir when server negotiates
-buffer size to small to fit filename. Add support for reading POSIX ACLs from
+buffer size too small to fit filename. Add support for reading POSIX ACLs from
 the server (add also acl and noacl mount options).
 
 Version 1.24
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 7f5607a..03b6019 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -462,7 +462,7 @@ accessed.
 "Anonymous" shows the amount of memory that does not belong to any file.  Even
 a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE
 and a page is modified, the file page is replaced by a private anonymous copy.
-"AnonHugePages" shows the ammount of memory backed by transparent hugepage.
+"AnonHugePages" shows the amount of memory backed by transparent hugepage.
 "Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by
 hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical
 reasons. And these are not included in {Shared,Private}_{Clean,Dirty} field.
@@ -1899,7 +1899,7 @@ hidepid=1 means users may not access any /proc/<pid>/ directories but their
 own.  Sensitive files like cmdline, sched*, status are now protected against
 other users.  This makes it impossible to learn whether any user runs
 specific program (given the program doesn't reveal itself by its behaviour).
-As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
+As an additional bonus, as /proc/<pid>/cmdline is inaccessible for other users,
 poorly written programs passing sensitive information via program arguments are
 now protected against local eavesdroppers.
 
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 4164bd6..ec67866 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -1014,7 +1014,7 @@ struct dentry_operations {
  Useful for some pseudo filesystems (sockfs, pipefs, ...) to delay
  pathname generation. (Instead of doing it when dentry is created,
  it's done only when the path is needed.). Real filesystems probably
- dont want to use it, because their dentries are present in global
+ don't want to use it, because their dentries are present in global
  dcache hash, so their hash should be an invariant. As no lock is
  held, d_dname() should not try to modify the dentry itself, unless
  appropriate SMP safety is used. CAUTION : d_path() logic is quite
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 26/41] Documentation: kasan: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/kasan.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/kasan.txt b/Documentation/kasan.txt
index 7dd95b3..9c696e4 100644
--- a/Documentation/kasan.txt
+++ b/Documentation/kasan.txt
@@ -116,7 +116,7 @@ Memory state around the buggy address:
  ffff8800693bc800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ==================================================================
 
-The header of the report discribe what kind of bug happened and what kind of
+The header of the report describe what kind of bug happened and what kind of
 access caused it. It's followed by the description of the accessed slub object
 (see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and
 the description of the accessed memory page.
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 23/41] Documentation: DocBook: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/DocBook/media/dvb/net.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/DocBook/media/dvb/net.xml b/Documentation/DocBook/media/dvb/net.xml
index d2e44b7..da095ed 100644
--- a/Documentation/DocBook/media/dvb/net.xml
+++ b/Documentation/DocBook/media/dvb/net.xml
@@ -15,7 +15,7 @@
     that are present on the transport stream. This is done through
     <constant>/dev/dvb/adapter?/net?</constant> device node.
     The data will be available via virtual <constant>dvb?_?</constant>
-    network interfaces, and will be controled/routed via the standard
+    network interfaces, and will be controlled/routed via the standard
     ip tools (like ip, route, netstat, ifconfig, etc).</para>
 <para> Data types and and ioctl definitions are defined via
     <constant>linux/dvb/net.h</constant> header.</para>
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 25/41] Documentation: filesystems: fix spelling mistakes

Steve French-2
In reply to this post by Eric Engestrom-2
Reviewed-by: Steve French <[hidden email]>

On Sun, Apr 24, 2016 at 7:24 PM, Eric Engestrom <[hidden email]> wrote:

> Signed-off-by: Eric Engestrom <[hidden email]>
> ---
>  Documentation/filesystems/autofs4.txt  | 6 +++---
>  Documentation/filesystems/cifs/CHANGES | 2 +-
>  Documentation/filesystems/proc.txt     | 4 ++--
>  Documentation/filesystems/vfs.txt      | 2 +-
>  4 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/filesystems/autofs4.txt b/Documentation/filesystems/autofs4.txt
> index 39d02e1..25fe9db 100644
> --- a/Documentation/filesystems/autofs4.txt
> +++ b/Documentation/filesystems/autofs4.txt
> @@ -225,7 +225,7 @@ unmount any filesystems mounted on the autofs filesystem or remove any
>  symbolic links or empty directories any time it likes.  If the unmount
>  or removal is successful the filesystem will be returned to the state
>  it was before the mount or creation, so that any access of the name
> -will trigger normal auto-mount processing.  In particlar, `rmdir` and
> +will trigger normal auto-mount processing.  In particular, `rmdir` and
>  `unlink` do not leave negative entries in the dcache as a normal
>  filesystem would, so an attempt to access a recently-removed object is
>  passed to autofs for handling.
> @@ -242,7 +242,7 @@ time stamp on each directory or symlink.  For symlinks it genuinely
>  does record the last time the symlink was "used" or followed to find
>  out where it points to.  For directories the field is a slight
>  misnomer.  It actually records the last time that autofs checked if
> -the directory or one of its descendents was busy and found that it
> +the directory or one of its descendants was busy and found that it
>  was.  This is just as useful and doesn't require updating the field so
>  often.
>
> @@ -255,7 +255,7 @@ up.
>
>  There is an option with indirect mounts to consider each of the leaves
>  that has been mounted on instead of considering the top-level names.
> -This is intended for compatability with version 4 of autofs and should
> +This is intended for compatibility with version 4 of autofs and should
>  be considered as deprecated.
>
>  When autofs considers a directory it checks the `last_used` time and
> diff --git a/Documentation/filesystems/cifs/CHANGES b/Documentation/filesystems/cifs/CHANGES
> index bc0025c..fe8f1ed 100644
> --- a/Documentation/filesystems/cifs/CHANGES
> +++ b/Documentation/filesystems/cifs/CHANGES
> @@ -455,7 +455,7 @@ Fix internationalization problem in cifs readdir with filenames that map to
>  longer UTF-8 strings than the string on the wire was in Unicode.  Add workaround
>  for readdir to netapp servers. Fix search rewind (seek into readdir to return
>  non-consecutive entries).  Do not do readdir when server negotiates
> -buffer size to small to fit filename. Add support for reading POSIX ACLs from
> +buffer size too small to fit filename. Add support for reading POSIX ACLs from
>  the server (add also acl and noacl mount options).
>
>  Version 1.24
> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
> index 7f5607a..03b6019 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -462,7 +462,7 @@ accessed.
>  "Anonymous" shows the amount of memory that does not belong to any file.  Even
>  a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE
>  and a page is modified, the file page is replaced by a private anonymous copy.
> -"AnonHugePages" shows the ammount of memory backed by transparent hugepage.
> +"AnonHugePages" shows the amount of memory backed by transparent hugepage.
>  "Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by
>  hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical
>  reasons. And these are not included in {Shared,Private}_{Clean,Dirty} field.
> @@ -1899,7 +1899,7 @@ hidepid=1 means users may not access any /proc/<pid>/ directories but their
>  own.  Sensitive files like cmdline, sched*, status are now protected against
>  other users.  This makes it impossible to learn whether any user runs
>  specific program (given the program doesn't reveal itself by its behaviour).
> -As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
> +As an additional bonus, as /proc/<pid>/cmdline is inaccessible for other users,
>  poorly written programs passing sensitive information via program arguments are
>  now protected against local eavesdroppers.
>
> diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
> index 4164bd6..ec67866 100644
> --- a/Documentation/filesystems/vfs.txt
> +++ b/Documentation/filesystems/vfs.txt
> @@ -1014,7 +1014,7 @@ struct dentry_operations {
>         Useful for some pseudo filesystems (sockfs, pipefs, ...) to delay
>         pathname generation. (Instead of doing it when dentry is created,
>         it's done only when the path is needed.). Real filesystems probably
> -       dont want to use it, because their dentries are present in global
> +       don't want to use it, because their dentries are present in global
>         dcache hash, so their hash should be an invariant. As no lock is
>         held, d_dname() should not try to modify the dentry itself, unless
>         appropriate SMP safety is used. CAUTION : d_path() logic is quite
> --
> 2.8.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to [hidden email]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



--
Thanks,

Steve
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 04/41] Documentation: cgroup: fix spelling mistakes

Randy Dunlap-3
In reply to this post by Eric Engestrom-2
On 04/24/16 17:24, Eric Engestrom wrote:

> @@ -1123,7 +1123,7 @@ writeback as follows.
>  
>  6-1. Basics
>  
> -cgroup namespace provides a mechanism to virtualize the view of the
> +cgroup namespace provides a mechanism to virtualise the view of the
>  "/proc/$PID/cgroup" file and cgroup mounts.  The CLONE_NEWCGROUP clone
>  flag can be used with clone(2) and unshare(2) to create a new cgroup
>  namespace.  The process running inside the cgroup namespace will have
> @@ -1256,7 +1256,7 @@ This will mount the unified cgroup hierarchy with cgroupns root as the
>  filesystem root.  The process needs CAP_SYS_ADMIN against its user and
>  mount namespaces.
>  
> -The virtualization of /proc/self/cgroup file combined with restricting
> +The virtualisation of /proc/self/cgroup file combined with restricting
>  the view of cgroup hierarchy by namespace-private cgroupfs mount
>  provides a properly isolated cgroup view inside the container.

We generally accept British or American spellings, so these changes
are not needed.


--
~Randy
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 09/41] Documentation: dt: clock: fix spelling mistakes

Randy Dunlap-3
In reply to this post by Eric Engestrom-2
On 04/24/16 17:24, Eric Engestrom wrote:

> Signed-off-by: Eric Engestrom <[hidden email]>
> ---
>  Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt | 2 +-
>  Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt | 2 +-
>  Documentation/devicetree/bindings/clock/st/st,clkgen.txt        | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt b/Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt
> index 0c2bf5e..7f36853 100644
> --- a/Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt
> +++ b/Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt
> @@ -16,7 +16,7 @@ Required Properties:
>  Optional Properties:
>  
>  - rockchip,grf: phandle to the syscon managing the "general register files"
> -  If missing pll rates are not changable, due to the missing pll lock status.
> +  If missing pll rates are not changeable, due to the missing pll lock status.
>  
>  Each clock is assigned an identifier and client nodes can use this identifier
>  to specify the clock which they consume. All available clocks are defined as
> diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt b/Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt
> index c9fbb76..8cb47c3 100644
> --- a/Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt
> +++ b/Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt
> @@ -15,7 +15,7 @@ Required Properties:
>  Optional Properties:
>  
>  - rockchip,grf: phandle to the syscon managing the "general register files"
> -  If missing pll rates are not changable, due to the missing pll lock status.
> +  If missing pll rates are not changeable, due to the missing pll lock status.
>  
>  Each clock is assigned an identifier and client nodes can use this identifier
>  to specify the clock which they consume. All available clocks are defined as
> diff --git a/Documentation/devicetree/bindings/clock/st/st,clkgen.txt b/Documentation/devicetree/bindings/clock/st/st,clkgen.txt
> index 78978f1..426bdda 100644
> --- a/Documentation/devicetree/bindings/clock/st/st,clkgen.txt
> +++ b/Documentation/devicetree/bindings/clock/st/st,clkgen.txt
> @@ -40,7 +40,7 @@ address is common of all subnode.
>   };
>  
>  This binding uses the common clock binding[1].
> -Each subnode should use the binding discribe in [2]..[7]
> +Each subnode should use the binding describe in [2]..[7]

described ?

>  
>  [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
>  [2] Documentation/devicetree/bindings/clock/st,clkgen-divmux.txt
>


--
~Randy
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 19/41] Documentation: dt: opp: fix spelling mistake

viresh kumar
In reply to this post by Eric Engestrom-2
On 25-04-16, 01:24, Eric Engestrom wrote:

> Signed-off-by: Eric Engestrom <[hidden email]>
> ---
>  Documentation/devicetree/bindings/opp/opp.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
> index 601256f..ee91cbd 100644
> --- a/Documentation/devicetree/bindings/opp/opp.txt
> +++ b/Documentation/devicetree/bindings/opp/opp.txt
> @@ -45,7 +45,7 @@ Devices supporting OPPs must set their "operating-points-v2" property with
>  phandle to a OPP table in their DT node. The OPP core will use this phandle to
>  find the operating points for the device.
>  
> -If required, this can be extended for SoC vendor specfic bindings. Such bindings
> +If required, this can be extended for SoC vendor specific bindings. Such bindings
>  should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt
>  and should have a compatible description like: "operating-points-v2-<vendor>".

Acked-by: Viresh Kumar <[hidden email]>

--
viresh
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 26/41] Documentation: kasan: fix spelling mistake

Randy Dunlap-3
In reply to this post by Eric Engestrom-2
On 04/24/16 17:24, Eric Engestrom wrote:

> Signed-off-by: Eric Engestrom <[hidden email]>
> ---
>  Documentation/kasan.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/kasan.txt b/Documentation/kasan.txt
> index 7dd95b3..9c696e4 100644
> --- a/Documentation/kasan.txt
> +++ b/Documentation/kasan.txt
> @@ -116,7 +116,7 @@ Memory state around the buggy address:
>   ffff8800693bc800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>  ==================================================================
>  
> -The header of the report discribe what kind of bug happened and what kind of
> +The header of the report describe what kind of bug happened and what kind of

describes

>  access caused it. It's followed by the description of the accessed slub object
>  (see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and
>  the description of the accessed memory page.
>


--
~Randy
Reply | Threaded
Open this post in threaded view
|

[PATCH 27/41] Documentation: laptops: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/laptops/toshiba_haps.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/laptops/toshiba_haps.txt b/Documentation/laptops/toshiba_haps.txt
index 11dbcfd..0c1d88d 100644
--- a/Documentation/laptops/toshiba_haps.txt
+++ b/Documentation/laptops/toshiba_haps.txt
@@ -19,7 +19,7 @@ Author: Azael Avalos <[hidden email]>
 --------------
 
 This driver provides support for the accelerometer found in various Toshiba
-laptops, being called "Toshiba HDD Protection - Shock Sensor" officialy,
+laptops, being called "Toshiba HDD Protection - Shock Sensor" officially,
 and detects laptops automatically with this device.
 On Windows, Toshiba provided software monitors this device and provides
 automatic HDD protection (head unload) on sudden moves or harsh vibrations,
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 28/41] Documentation: locking: fix spelling mistakes

Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/locking/lockdep-design.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/locking/lockdep-design.txt b/Documentation/locking/lockdep-design.txt
index 5001280..9de1c15 100644
--- a/Documentation/locking/lockdep-design.txt
+++ b/Documentation/locking/lockdep-design.txt
@@ -97,7 +97,7 @@ between any two lock-classes:
    <hardirq-safe>   ->  <hardirq-unsafe>
    <softirq-safe>   ->  <softirq-unsafe>
 
-The first rule comes from the fact the a hardirq-safe lock could be
+The first rule comes from the fact that a hardirq-safe lock could be
 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
 lock could be taken by an softirq context, interrupting a softirq-unsafe
@@ -220,7 +220,7 @@ calculated, which hash is unique for every lock chain. The hash value,
 when the chain is validated for the first time, is then put into a hash
 table, which hash-table can be checked in a lockfree manner. If the
 locking chain occurs again later on, the hash table tells us that we
-dont have to validate the chain again.
+don't have to validate the chain again.
 
 Troubleshooting:
 ----------------
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 37/41] Documentation: video4linux: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/video4linux/vivid.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/video4linux/vivid.txt b/Documentation/video4linux/vivid.txt
index e35d376..8da5d2a 100644
--- a/Documentation/video4linux/vivid.txt
+++ b/Documentation/video4linux/vivid.txt
@@ -294,7 +294,7 @@ the result will be.
 
 These inputs support all combinations of the field setting. Special care has
 been taken to faithfully reproduce how fields are handled for the different
-TV standards. This is particularly noticable when generating a horizontally
+TV standards. This is particularly noticeable when generating a horizontally
 moving image so the temporal effect of using interlaced formats becomes clearly
 visible. For 50 Hz standards the top field is the oldest and the bottom field
 is the newest in time. For 60 Hz standards that is reversed: the bottom field
@@ -313,7 +313,7 @@ will be SMPTE-170M.
 The pixel aspect ratio will depend on the TV standard. The video aspect ratio
 can be selected through the 'Standard Aspect Ratio' Vivid control.
 Choices are '4x3', '16x9' which will give letterboxed widescreen video and
-'16x9 Anomorphic' which will give full screen squashed anamorphic widescreen
+'16x9 Anamorphic' which will give full screen squashed anamorphic widescreen
 video that will need to be scaled accordingly.
 
 The TV 'tuner' supports a frequency range of 44-958 MHz. Channels are available
@@ -862,7 +862,7 @@ RDS Radio Text:
 RDS Stereo:
 RDS Artificial Head:
 RDS Compressed:
-RDS Dymanic PTY:
+RDS Dynamic PTY:
 RDS Traffic Announcement:
 RDS Traffic Program:
 RDS Music: these are all controls that set the RDS data that is transmitted by
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 41/41] Documentation: xillybus: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/xillybus.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/xillybus.txt b/Documentation/xillybus.txt
index 81d111b..1660145 100644
--- a/Documentation/xillybus.txt
+++ b/Documentation/xillybus.txt
@@ -215,7 +215,7 @@ in xillybus_core.c as follows:
   choice is a non-zero value, to match standard UNIX behavior.
 
 * synchronous: A non-zero value means that the pipe is synchronous. See
-  Syncronization above.
+  Synchronization above.
 
 * bufsize: Each DMA buffer's size. Always a power of two.
 
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 38/41] Documentation: virtual: fix spelling mistake

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/virtual/kvm/devices/s390_flic.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/virtual/kvm/devices/s390_flic.txt b/Documentation/virtual/kvm/devices/s390_flic.txt
index e3e314c..13a1261 100644
--- a/Documentation/virtual/kvm/devices/s390_flic.txt
+++ b/Documentation/virtual/kvm/devices/s390_flic.txt
@@ -68,7 +68,7 @@ struct kvm_s390_io_adapter {
 
   KVM_DEV_FLIC_ADAPTER_MODIFY
     Modifies attributes of an existing I/O adapter interrupt source. Takes
-    a kvm_s390_io_adapter_req specifiying the adapter and the operation:
+    a kvm_s390_io_adapter_req specifying the adapter and the operation:
 
 struct kvm_s390_io_adapter_req {
  __u32 id;
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 39/41] Documentation: vm: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/vm/transhuge.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
index d9cb65c..2f383f6 100644
--- a/Documentation/vm/transhuge.txt
+++ b/Documentation/vm/transhuge.txt
@@ -340,7 +340,7 @@ unaffected. libhugetlbfs will also work fine as usual.
 
 == Graceful fallback ==
 
-Code walking pagetables but unware about huge pmds can simply call
+Code walking pagetables but unaware about huge pmds can simply call
 split_huge_pmd(vma, pmd, addr) where the pmd is the one returned by
 pmd_offset. It's trivial to make the code transparent hugepage aware
 by just grepping for "pmd_offset" and adding split_huge_pmd where
@@ -414,7 +414,7 @@ tracking. The alternative is alter ->_mapcount in all subpages on each
 map/unmap of the whole compound page.
 
 We set PG_double_map when a PMD of the page got split for the first time,
-but still have PMD mapping. The addtional references go away with last
+but still have PMD mapping. The additional references go away with last
 compound_mapcount.
 
 split_huge_page internally has to distribute the refcounts in the head
@@ -433,7 +433,7 @@ We safe against physical memory scanners too: the only legitimate way
 scanner can get reference to a page is get_page_unless_zero().
 
 All tail pages has zero ->_count until atomic_add(). It prevent scanner
-from geting reference to tail page up to the point. After the atomic_add()
+from getting reference to tail page up to the point. After the atomic_add()
 we don't care about ->_count value.  We already known how many references
 with should uncharge from head page.
 
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 40/41] Documentation: x86: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/x86/intel_mpx.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/x86/intel_mpx.txt b/Documentation/x86/intel_mpx.txt
index 818518a..1a5a121 100644
--- a/Documentation/x86/intel_mpx.txt
+++ b/Documentation/x86/intel_mpx.txt
@@ -136,7 +136,7 @@ A: MPX-enabled application will possibly create a lot of bounds tables in
    If we were to preallocate them for the 128TB of user virtual address
    space, we would need to reserve 512TB+2GB, which is larger than the
    entire virtual address space today. This means they can not be reserved
-   ahead of time. Also, a single process's pre-popualated bounds directory
+   ahead of time. Also, a single process's pre-populated bounds directory
    consumes 2GB of virtual *AND* physical memory. IOW, it's completely
    infeasible to prepopulate bounds directories.
 
@@ -151,7 +151,7 @@ A: This would work if we could hook the site of each and every memory
    these calls.
 
 Q: Could a bounds fault be handed to userspace and the tables allocated
-   there in a signal handler intead of in the kernel?
+   there in a signal handler instead of in the kernel?
 A: mmap() is not on the list of safe async handler functions and even
    if mmap() would work it still requires locking or nasty tricks to
    keep track of the allocation state there.
--
2.8.0

Reply | Threaded
Open this post in threaded view
|

[PATCH 30/41] Documentation: networking: fix spelling mistakes

Eric Engestrom-2
In reply to this post by Eric Engestrom-2
Signed-off-by: Eric Engestrom <[hidden email]>
---
 Documentation/networking/altera_tse.txt | 6 +++---
 Documentation/networking/ipvlan.txt     | 6 +++---
 Documentation/networking/pktgen.txt     | 6 +++---
 Documentation/networking/vrf.txt        | 2 +-
 Documentation/networking/xfrm_sync.txt  | 6 +++---
 5 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/Documentation/networking/altera_tse.txt b/Documentation/networking/altera_tse.txt
index 3f24df8..50b8589 100644
--- a/Documentation/networking/altera_tse.txt
+++ b/Documentation/networking/altera_tse.txt
@@ -6,7 +6,7 @@ This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
 using the SGDMA and MSGDMA soft DMA IP components. The driver uses the
 platform bus to obtain component resources. The designs used to test this
 driver were built for a Cyclone(R) V SOC FPGA board, a Cyclone(R) V FPGA board,
-and tested with ARM and NIOS processor hosts seperately. The anticipated use
+and tested with ARM and NIOS processor hosts separately. The anticipated use
 cases are simple communications between an embedded system and an external peer
 for status and simple configuration of the embedded system.
 
@@ -65,14 +65,14 @@ Driver parameters can be also passed in command line by using:
 4.1) Transmit process
 When the driver's transmit routine is called by the kernel, it sets up a
 transmit descriptor by calling the underlying DMA transmit routine (SGDMA or
-MSGDMA), and initites a transmit operation. Once the transmit is complete, an
+MSGDMA), and initiates a transmit operation. Once the transmit is complete, an
 interrupt is driven by the transmit DMA logic. The driver handles the transmit
 completion in the context of the interrupt handling chain by recycling
 resource required to send and track the requested transmit operation.
 
 4.2) Receive process
 The driver will post receive buffers to the receive DMA logic during driver
-intialization. Receive buffers may or may not be queued depending upon the
+initialization. Receive buffers may or may not be queued depending upon the
 underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
 to queue receive buffers to the SGDMA receive logic). When a packet is
 received, the DMA logic generates an interrupt. The driver handles a receive
diff --git a/Documentation/networking/ipvlan.txt b/Documentation/networking/ipvlan.txt
index cf99639..14422f8 100644
--- a/Documentation/networking/ipvlan.txt
+++ b/Documentation/networking/ipvlan.txt
@@ -8,7 +8,7 @@ Initial Release:
  This is conceptually very similar to the macvlan driver with one major
 exception of using L3 for mux-ing /demux-ing among slaves. This property makes
 the master device share the L2 with it's slave devices. I have developed this
-driver in conjuntion with network namespaces and not sure if there is use case
+driver in conjunction with network namespaces and not sure if there is use case
 outside of it.
 
 
@@ -42,7 +42,7 @@ out. In this mode the slaves will RX/TX multicast and broadcast (if applicable)
 as well.
 
 4.2 L3 mode:
- In this mode TX processing upto L3 happens on the stack instance attached
+ In this mode TX processing up to L3 happens on the stack instance attached
 to the slave device and packets are switched to the stack instance of the
 master device for the L2 processing and routing from that instance will be
 used before packets are queued on the outbound device. In this mode the slaves
@@ -56,7 +56,7 @@ situations defines your use case then you can choose to use ipvlan -
  (a) The Linux host that is connected to the external switch / router has
 policy configured that allows only one mac per port.
  (b) No of virtual devices created on a master exceed the mac capacity and
-puts the NIC in promiscous mode and degraded performance is a concern.
+puts the NIC in promiscuous mode and degraded performance is a concern.
  (c) If the slave device is to be put into the hostile / untrusted network
 namespace where L2 on the slave could be changed / misused.
 
diff --git a/Documentation/networking/pktgen.txt b/Documentation/networking/pktgen.txt
index f4be85e..2c4e335 100644
--- a/Documentation/networking/pktgen.txt
+++ b/Documentation/networking/pktgen.txt
@@ -67,12 +67,12 @@ The two basic thread commands are:
  * add_device DEVICE@NAME -- adds a single device
  * rem_device_all         -- remove all associated devices
 
-When adding a device to a thread, a corrosponding procfile is created
+When adding a device to a thread, a corresponding procfile is created
 which is used for configuring this device. Thus, device names need to
 be unique.
 
 To support adding the same device to multiple threads, which is useful
-with multi queue NICs, a the device naming scheme is extended with "@":
+with multi queue NICs, the device naming scheme is extended with "@":
  device@something
 
 The part after "@" can be anything, but it is custom to use the thread
@@ -221,7 +221,7 @@ Sample scripts
 
 A collection of tutorial scripts and helpers for pktgen is in the
 samples/pktgen directory. The helper parameters.sh file support easy
-and consistant parameter parsing across the sample scripts.
+and consistent parameter parsing across the sample scripts.
 
 Usage example and help:
  ./pktgen_sample01_simple.sh -i eth4 -m 00:1B:21:3C:9D:F8 -d 192.168.8.2
diff --git a/Documentation/networking/vrf.txt b/Documentation/networking/vrf.txt
index d52aa10..5da679c 100644
--- a/Documentation/networking/vrf.txt
+++ b/Documentation/networking/vrf.txt
@@ -41,7 +41,7 @@ using an rx_handler which gives the impression that packets flow through
 the VRF device. Similarly on egress routing rules are used to send packets
 to the VRF device driver before getting sent out the actual interface. This
 allows tcpdump on a VRF device to capture all packets into and out of the
-VRF as a whole.[1] Similiarly, netfilter [2] and tc rules can be applied
+VRF as a whole.[1] Similarly, netfilter [2] and tc rules can be applied
 using the VRF device to specify rules that apply to the VRF domain as a whole.
 
 [1] Packets in the forwarded state do not flow through the device, so those
diff --git a/Documentation/networking/xfrm_sync.txt b/Documentation/networking/xfrm_sync.txt
index d7aac9d..8d88e0f 100644
--- a/Documentation/networking/xfrm_sync.txt
+++ b/Documentation/networking/xfrm_sync.txt
@@ -4,7 +4,7 @@ Krisztian <[hidden email]> and others and additional patches
 from Jamal <[hidden email]>.
 
 The end goal for syncing is to be able to insert attributes + generate
-events so that the an SA can be safely moved from one machine to another
+events so that the SA can be safely moved from one machine to another
 for HA purposes.
 The idea is to synchronize the SA so that the takeover machine can do
 the processing of the SA as accurate as possible if it has access to it.
@@ -13,7 +13,7 @@ We already have the ability to generate SA add/del/upd events.
 These patches add ability to sync and have accurate lifetime byte (to
 ensure proper decay of SAs) and replay counters to avoid replay attacks
 with as minimal loss at failover time.
-This way a backup stays as closely uptodate as an active member.
+This way a backup stays as closely up-to-date as an active member.
 
 Because the above items change for every packet the SA receives,
 it is possible for a lot of the events to be generated.
@@ -163,7 +163,7 @@ If you have an SA that is getting hit by traffic in bursts such that
 there is a period where the timer threshold expires with no packets
 seen, then an odd behavior is seen as follows:
 The first packet arrival after a timer expiry will trigger a timeout
-aevent; i.e we dont wait for a timeout period or a packet threshold
+event; i.e we don't wait for a timeout period or a packet threshold
 to be reached. This is done for simplicity and efficiency reasons.
 
 -JHS
--
2.8.0

12345