The following typos and other spelling mistakes were mostly found using
`codespell` [1], and the rest was found using vim's `spell` check.
I left out a bunch of "thru" -> "through", thinking it could just be
seen as regional preference (US vs UK). Should I send those as well?
Those patches can be applied independently (obviously), so there is
no need to wait for the whole series to be ack'ed.
Cheers,
Eric
[1] https://github.com/lucasdemarchi/codespell
Eric Engestrom (41):
Documentation: debugfs: fix spelling mistake
Documentation: sysfs: fix spelling mistakes
Documentation: arm: fix spelling mistakes
Documentation: cgroup: fix spelling mistakes
Documentation: cpu-hotplug: fix spelling mistake
Documentation: device-mapper: fix spelling mistakes
Documentation: dt: arc: fix spelling mistakes
Documentation: dt: arm: fix spelling mistakes
Documentation: dt: clock: fix spelling mistakes
Documentation: dt: display: fix spelling mistake
Documentation: dt: dma: fix spelling mistake
Documentation: dt: input: fix spelling mistakes
Documentation: dt: interrupt-controller: fix spelling mistakes
Documentation: dt: media: fix spelling mistake
Documentation: dt: mfd: fix spelling mistakes
Documentation: dt: mmc: fix spelling mistake
Documentation: dt: mtd: fix spelling mistake
Documentation: dt: net: fix spelling mistakes
Documentation: dt: opp: fix spelling mistake
Documentation: dt: pinctrl: fix spelling mistake
Documentation: dt: power: fix spelling mistake
Documentation: dt: soc: fix spelling mistakes
Documentation: DocBook: fix spelling mistake
Documentation: fb: fix spelling mistakes
Documentation: filesystems: fix spelling mistakes
Documentation: kasan: fix spelling mistake
Documentation: laptops: fix spelling mistake
Documentation: locking: fix spelling mistakes
Documentation: lzo: fix spelling mistakes
Documentation: networking: fix spelling mistakes
Documentation: power: fix spelling mistake
Documentation: pps: fix spelling mistake
Documentation: RCU: fix spelling mistake
Documentation: robust-futexes: fix spelling mistakes
Documentation: scsi: fix spelling mistakes
Documentation: sound: fix spelling mistakes
Documentation: video4linux: fix spelling mistakes
Documentation: virtual: fix spelling mistake
Documentation: vm: fix spelling mistakes
Documentation: x86: fix spelling mistakes
Documentation: xillybus: fix spelling mistake
Documentation/ABI/testing/debugfs-driver-genwqe | 2 +-
.../ABI/testing/sysfs-bus-coresight-devices-etm4x | 2 +-
.../ABI/testing/sysfs-bus-event_source-devices-events | 4 ++--
.../ABI/testing/sysfs-bus-event_source-devices-hv_24x7 | 2 +-
Documentation/ABI/testing/sysfs-driver-tegra-fuse | 2 +-
Documentation/ABI/testing/sysfs-fs-xfs | 2 +-
Documentation/DocBook/media/dvb/net.xml | 2 +-
Documentation/RCU/stallwarn.txt | 2 +-
Documentation/arm/Atmel/README | 2 +-
Documentation/arm/keystone/knav-qmss.txt | 2 +-
Documentation/cgroup-v2.txt | 16 ++++++++--------
Documentation/cpu-hotplug.txt | 2 +-
Documentation/device-mapper/cache-policies.txt | 4 ++--
Documentation/device-mapper/statistics.txt | 2 +-
Documentation/devicetree/bindings/arc/archs-pct.txt | 2 +-
Documentation/devicetree/bindings/arc/pct.txt | 2 +-
Documentation/devicetree/bindings/arm/cci.txt | 2 +-
Documentation/devicetree/bindings/arm/spear-misc.txt | 2 +-
.../devicetree/bindings/clock/rockchip,rk3188-cru.txt | 2 +-
.../devicetree/bindings/clock/rockchip,rk3288-cru.txt | 2 +-
Documentation/devicetree/bindings/clock/st/st,clkgen.txt | 2 +-
.../devicetree/bindings/display/exynos/exynos_dsim.txt | 2 +-
.../devicetree/bindings/dma/xilinx/xilinx_dma.txt | 2 +-
Documentation/devicetree/bindings/input/ads7846.txt | 2 +-
.../bindings/input/touchscreen/fsl-mx25-tcq.txt | 2 +-
.../bindings/interrupt-controller/ti,omap4-wugen-mpu | 4 ++--
Documentation/devicetree/bindings/media/xilinx/video.txt | 2 +-
Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 4 ++--
.../devicetree/bindings/mmc/mmc-pwrseq-emmc.txt | 2 +-
Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt | 2 +-
.../devicetree/bindings/net/hisilicon-hns-nic.txt | 2 +-
Documentation/devicetree/bindings/net/stmmac.txt | 4 ++--
Documentation/devicetree/bindings/net/ti,dp83867.txt | 2 +-
Documentation/devicetree/bindings/opp/opp.txt | 2 +-
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 2 +-
.../devicetree/bindings/power/qcom,coincell-charger.txt | 2 +-
.../bindings/soc/ti/keystone-navigator-qmss.txt | 6 +++---
Documentation/fb/udlfb.txt | 6 +++---
Documentation/filesystems/autofs4.txt | 6 +++---
Documentation/filesystems/cifs/CHANGES | 2 +-
Documentation/filesystems/proc.txt | 4 ++--
Documentation/filesystems/vfs.txt | 2 +-
Documentation/kasan.txt | 2 +-
Documentation/laptops/toshiba_haps.txt | 2 +-
Documentation/locking/lockdep-design.txt | 4 ++--
Documentation/lzo.txt | 4 ++--
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 +++---
Documentation/power/opp.txt | 2 +-
Documentation/pps/pps.txt | 2 +-
Documentation/robust-futexes.txt | 6 +++---
Documentation/scsi/ChangeLog.megaraid_sas | 16 ++++++++--------
Documentation/sound/alsa/compress_offload.txt | 2 +-
Documentation/sound/alsa/soc/dapm.txt | 2 +-
Documentation/sound/alsa/soc/overview.txt | 2 +-
Documentation/video4linux/vivid.txt | 6 +++---
Documentation/virtual/kvm/devices/s390_flic.txt | 2 +-
Documentation/vm/transhuge.txt | 6 +++---
Documentation/x86/intel_mpx.txt | 4 ++--
Documentation/xillybus.txt | 2 +-
63 files changed, 106 insertions(+), 106 deletions(-)
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/ABI/testing/debugfs-driver-genwqe | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/debugfs-driver-genwqe b/Documentation/ABI/testing/debugfs-driver-genwqe
index 1c2f256..b45b016 100644
--- a/Documentation/ABI/testing/debugfs-driver-genwqe
+++ b/Documentation/ABI/testing/debugfs-driver-genwqe
@@ -31,7 +31,7 @@ What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_regs
Date: Oct 2013
Contact: [email protected]
Description: Dump of the error registers before the last reset of
- the card occured.
+ the card occurred.
Only available for PF.
What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid0
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x | 2 +-
Documentation/ABI/testing/sysfs-bus-event_source-devices-events | 4 ++--
Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 | 2 +-
Documentation/ABI/testing/sysfs-driver-tegra-fuse | 2 +-
Documentation/ABI/testing/sysfs-fs-xfs | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
index 2355ed8..19b83f4 100644
--- a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
+++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
@@ -378,7 +378,7 @@ Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <[email protected]>
Description: (R) Returns the maximum size of the data value, data address,
- VMID, context ID and instuction address in the trace unit
+ VMID, context ID and instruction address in the trace unit
(0x1E8). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/trcidr/trcidr3
diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
index 505f080..77de58d 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
@@ -47,7 +47,7 @@ Description: Per-pmu performance monitoring events specific to the running syste
If a <term> is specified alone (without an assigned value), it
is implied that 0x1 is assigned to that <term>.
- Examples (each of these lines would be in a seperate file):
+ Examples (each of these lines would be in a separate file):
event=0x2abc
event=0x423,inv,cmask=0x3
@@ -83,7 +83,7 @@ Description: Perf event scaling factors
A string representing a floating point value expressed in
scientific notation to be multiplied by the event count
- recieved from the kernel to match the unit specified in the
+ received from the kernel to match the unit specified in the
<event>.unit file.
Example:
diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
index f893337..ec27c6c 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
@@ -4,7 +4,7 @@ Contact: Linux on PowerPC Developer List <[email protected]>
Description:
Provides access to the binary "24x7 catalog" provided by the
hypervisor on POWER7 and 8 systems. This catalog lists events
- avaliable from the powerpc "hv_24x7" pmu. Its format is
+ available from the powerpc "hv_24x7" pmu. Its format is
documented here:
https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h
diff --git a/Documentation/ABI/testing/sysfs-driver-tegra-fuse b/Documentation/ABI/testing/sysfs-driver-tegra-fuse
index 69f5af6..b8936fa 100644
--- a/Documentation/ABI/testing/sysfs-driver-tegra-fuse
+++ b/Documentation/ABI/testing/sysfs-driver-tegra-fuse
@@ -3,7 +3,7 @@ Date: February 2014
Contact: Peter De Schrijver <[email protected]>
Description: read-only access to the efuses on Tegra20, Tegra30, Tegra114
and Tegra124 SoC's from NVIDIA. The efuses contain write once
- data programmed at the factory. The data is layed out in 32bit
+ data programmed at the factory. The data is laid out in 32bit
words in LSB first format. Each bit represents a single value
as decoded from the fuse registers. Bits order/assignment
exactly matches the HW registers, including any unused bits.
diff --git a/Documentation/ABI/testing/sysfs-fs-xfs b/Documentation/ABI/testing/sysfs-fs-xfs
index ea0cc8c..f704925 100644
--- a/Documentation/ABI/testing/sysfs-fs-xfs
+++ b/Documentation/ABI/testing/sysfs-fs-xfs
@@ -33,7 +33,7 @@ Contact: [email protected]
Description:
The current state of the log write grant head. It
represents the total log reservation of all currently
- oustanding transactions, including regrants due to
+ outstanding transactions, including regrants due to
rolling transactions. The grant head is exported in
"cycle:bytes" format.
Users: xfstests
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/arm/Atmel/README | 2 +-
Documentation/arm/keystone/knav-qmss.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm/Atmel/README b/Documentation/arm/Atmel/README
index 0931cf7..adffac7 100644
--- a/Documentation/arm/Atmel/README
+++ b/Documentation/arm/Atmel/README
@@ -16,7 +16,7 @@ git branches/tags and email subject always contain this "at91" sub-string.
AT91 SoCs
---------
-Documentation and detailled datasheet for each product are available on
+Documentation and detailed datasheet for each product are available on
the Atmel website: http://www.atmel.com.
Flavors:
diff --git a/Documentation/arm/keystone/knav-qmss.txt b/Documentation/arm/keystone/knav-qmss.txt
index fcdb9fd..d15bf9a 100644
--- a/Documentation/arm/keystone/knav-qmss.txt
+++ b/Documentation/arm/keystone/knav-qmss.txt
@@ -36,7 +36,7 @@ accumulator channels defined in DTS (example in DT documentation) to monitor
CPPI/QMSS Low Level Driver document (docs/CPPI_QMSS_LLD_SDS.pdf) at
git://git.ti.com/keystone-rtos/qmss-lld.git
-k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
+k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports up to 48 accumulator
channels. This firmware is available under ti-keystone folder of
firmware.git at
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/cgroup-v2.txt | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
index 4cc07ce..c836b69 100644
--- a/Documentation/cgroup-v2.txt
+++ b/Documentation/cgroup-v2.txt
@@ -422,7 +422,7 @@ and is an example of this type.
3-2. Limits
-A child can only consume upto the configured amount of the resource.
+A child can only consume up to the configured amount of the resource.
Limits can be over-committed - the sum of the limits of children can
exceed the amount of resource available to the parent.
@@ -438,11 +438,11 @@ on an IO device and is an example of this type.
3-3. Protections
-A cgroup is protected to be allocated upto the configured amount of
+A cgroup is protected to be allocated up to the configured amount of
the resource if the usages of all its ancestors are under their
protected levels. Protections can be hard guarantees or best effort
soft boundaries. Protections can also be over-committed in which case
-only upto the amount available to the parent is protected among
+only up to the amount available to the parent is protected among
children.
Protections are in the range [0, max] and defaults to 0, which is
@@ -694,7 +694,7 @@ All time durations are in microseconds.
$MAX $PERIOD
- which indicates that the group may consume upto $MAX in each
+ which indicates that the group may consume up to $MAX in each
$PERIOD duration. "max" for $MAX indicates no limit. If only
one number is written, $MAX is updated.
@@ -713,7 +713,7 @@ All time durations are in microseconds.
$MAX $PERIOD
- which indicates that the group may consume upto $MAX in each
+ which indicates that the group may consume up to $MAX in each
$PERIOD duration. If only one number is written, $MAX is
updated.
@@ -923,7 +923,7 @@ PAGE_SIZE multiple when read back.
cgroups. The default is "max".
Swap usage hard limit. If a cgroup's swap usage reaches this
- limit, anonymous meomry of the cgroup will not be swapped out.
+ limit, anonymous memory of the cgroup will not be swapped out.
5-2-2. Usage Guidelines
@@ -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.
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/device-mapper/cache-policies.txt | 4 ++--
Documentation/device-mapper/statistics.txt | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/device-mapper/cache-policies.txt b/Documentation/device-mapper/cache-policies.txt
index e5062ad..e3a2063 100644
--- a/Documentation/device-mapper/cache-policies.txt
+++ b/Documentation/device-mapper/cache-policies.txt
@@ -11,7 +11,7 @@ Every bio that is mapped by the target is referred to the policy.
The policy can return a simple HIT or MISS or issue a migration.
Currently there's no way for the policy to issue background work,
-e.g. to start writing back dirty blocks that are going to be evicte
+e.g. to start writing back dirty blocks that are going to be evicted
soon.
Because we map bios, rather than requests it's easy for the policy
@@ -67,7 +67,7 @@ the entries (each hotspot block covers a larger area than a single
cache block).
All these mean smq uses ~25bytes per cache block. Still a lot of
-memory, but a substantial improvement nontheless.
+memory, but a substantial improvement nonetheless.
Level balancing:
MQ places entries in different levels of the multiqueue structures
diff --git a/Documentation/device-mapper/statistics.txt b/Documentation/device-mapper/statistics.txt
index 6f5ef94..170ac02 100644
--- a/Documentation/device-mapper/statistics.txt
+++ b/Documentation/device-mapper/statistics.txt
@@ -205,7 +205,7 @@ statistics on them:
dmsetup message vol 0 @stats_create - /100
-Set the auxillary data string to "foo bar baz" (the escape for each
+Set the auxiliary data string to "foo bar baz" (the escape for each
space must also be escaped, otherwise the shell will consume them):
dmsetup message vol 0 @stats_set_aux 0 foo\\ bar\\ baz
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/cpu-hotplug.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
index dd68821..12e0b8f 100644
--- a/Documentation/cpu-hotplug.txt
+++ b/Documentation/cpu-hotplug.txt
@@ -97,7 +97,7 @@ from the map depending on the event is hot-add/hot-remove. There are currently
no locking rules as of now. Typical usage is to init topology during boot,
at which time hotplug is disabled.
-You really dont need to manipulate any of the system cpu maps. They should
+You really don't need to manipulate any of the system cpu maps. They should
be read-only for most use. When setting up per-cpu resources almost always use
cpu_possible_mask/for_each_possible_cpu() to iterate.
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/arc/archs-pct.txt | 2 +-
Documentation/devicetree/bindings/arc/pct.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arc/archs-pct.txt b/Documentation/devicetree/bindings/arc/archs-pct.txt
index 1ae98b87..e4b9dce 100644
--- a/Documentation/devicetree/bindings/arc/archs-pct.txt
+++ b/Documentation/devicetree/bindings/arc/archs-pct.txt
@@ -2,7 +2,7 @@
The ARC HS can be configured with a pipeline performance monitor for counting
CPU and cache events like cache misses and hits. Like conventional PCT there
-are 100+ hardware conditions dynamically mapped to upto 32 counters.
+are 100+ hardware conditions dynamically mapped to up to 32 counters.
It also supports overflow interrupts.
Required properties:
diff --git a/Documentation/devicetree/bindings/arc/pct.txt b/Documentation/devicetree/bindings/arc/pct.txt
index 7b95884..4e874d9 100644
--- a/Documentation/devicetree/bindings/arc/pct.txt
+++ b/Documentation/devicetree/bindings/arc/pct.txt
@@ -2,7 +2,7 @@
The ARC700 can be configured with a pipeline performance monitor for counting
CPU and cache events like cache misses and hits. Like conventional PCT there
-are 100+ hardware conditions dynamically mapped to upto 32 counters
+are 100+ hardware conditions dynamically mapped to up to 32 counters
Note that:
* The ARC 700 PCT does not support interrupts; although HW events may be
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/arm/cci.txt | 2 +-
Documentation/devicetree/bindings/arm/spear-misc.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/cci.txt b/Documentation/devicetree/bindings/arm/cci.txt
index a1a5a7e..0f2153e 100644
--- a/Documentation/devicetree/bindings/arm/cci.txt
+++ b/Documentation/devicetree/bindings/arm/cci.txt
@@ -100,7 +100,7 @@ specific to ARM.
"arm,cci-400-pmu,r0"
"arm,cci-400-pmu,r1"
"arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
- secure acces to CCI registers
+ secure access to CCI registers
"arm,cci-500-pmu,r0"
"arm,cci-550-pmu,r0"
- reg:
diff --git a/Documentation/devicetree/bindings/arm/spear-misc.txt b/Documentation/devicetree/bindings/arm/spear-misc.txt
index cf64982..e404e25 100644
--- a/Documentation/devicetree/bindings/arm/spear-misc.txt
+++ b/Documentation/devicetree/bindings/arm/spear-misc.txt
@@ -6,4 +6,4 @@ few properties of different peripheral controllers.
misc node required properties:
- compatible Should be "st,spear1340-misc", "syscon".
-- reg: Address range of misc space upto 8K
+- reg: Address range of misc space up to 8K
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
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]
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
[2] Documentation/devicetree/bindings/clock/st,clkgen-divmux.txt
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt b/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
index 22756b3..a782659 100644
--- a/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
+++ b/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
@@ -41,7 +41,7 @@ Video interfaces:
endpoint node connected from mic node (reg = 0):
- remote-endpoint: specifies the endpoint in mic node. This node is required
for Exynos5433 mipi dsi. So mic can access to panel node
- thoughout this dsi node.
+ throughout this dsi node.
endpoint node connected to panel node (reg = 1):
- remote-endpoint: specifies the endpoint in panel node. This node is
required in all kinds of exynos mipi dsi to represent
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt b/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
index 2291c40..3cf0072d 100644
--- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
+++ b/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
@@ -7,7 +7,7 @@ Required properties:
- compatible: Should be "xlnx,axi-dma-1.00.a"
- #dma-cells: Should be <1>, see "dmas" property below
- reg: Should contain DMA registers location and length.
-- dma-channel child node: Should have atleast one channel and can have upto
+- dma-channel child node: Should have at least one channel and can have up to
two channels per device. This node specifies the properties of each
DMA channel (see child node properties below).
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/input/ads7846.txt | 2 +-
Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/input/ads7846.txt b/Documentation/devicetree/bindings/input/ads7846.txt
index c6cfe2e..9fc47b0 100644
--- a/Documentation/devicetree/bindings/input/ads7846.txt
+++ b/Documentation/devicetree/bindings/input/ads7846.txt
@@ -29,7 +29,7 @@ Optional properties:
ti,vref-delay-usecs vref supply delay in usecs, 0 for
external vref (u16).
ti,vref-mv The VREF voltage, in millivolts (u16).
- Set to 0 to use internal refernce
+ Set to 0 to use internal references
(ADS7846).
ti,keep-vref-on set to keep vref on for differential
measurements as well
diff --git a/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt b/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
index cdf05f9..abfcab3 100644
--- a/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
+++ b/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
@@ -15,7 +15,7 @@ Optional properties:
- fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
- fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
between 1 and 4096. It is the ratio between the internal reference voltage
- and the measured voltage after the plate was precharged. Resistence between
+ and the measured voltage after the plate was precharged. Resistance between
plates and therefore the voltage decreases with pressure so that a smaller
value is equivalent to a higher pressure.
- fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
.../devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
index 43effa0..18d4f40 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
+++ b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
@@ -4,7 +4,7 @@ All TI OMAP4/5 (and their derivatives) an interrupt controller that
routes interrupts to the GIC, and also serves as a wakeup source. It
is also referred to as "WUGEN-MPU", hence the name of the binding.
-Reguired properties:
+Required properties:
- compatible : should contain at least "ti,omap4-wugen-mpu" or
"ti,omap5-wugen-mpu"
@@ -20,7 +20,7 @@ Notes:
- Because this HW ultimately routes interrupts to the GIC, the
interrupt specifier must be that of the GIC.
- Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
- are explicitly forbiden.
+ are explicitly forbidden.
Example:
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/media/xilinx/video.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/xilinx/video.txt b/Documentation/devicetree/bindings/media/xilinx/video.txt
index cbd46fa..68ac210 100644
--- a/Documentation/devicetree/bindings/media/xilinx/video.txt
+++ b/Documentation/devicetree/bindings/media/xilinx/video.txt
@@ -20,7 +20,7 @@ The following properties are common to all Xilinx video IP cores.
- xlnx,video-format: This property represents a video format transmitted on an
AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
Video IP and System Design Guide" [UG934]. How the format relates to the IP
- core is decribed in the IP core bindings documentation.
+ core is described in the IP core bindings documentation.
- xlnx,video-width: This property qualifies the video format with the sample
width expressed as a number of bits per pixel component. All components must
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
index 5e97a95..b98b291 100644
--- a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
+++ b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
@@ -178,7 +178,7 @@ see regulator.txt - with additional custom properties described below:
- qcom,force-mode:
Usage: optional (default if no other qcom,force-mode is specified)
Value type: <u32>
- Defintion: indicates that the regulator should be forced to a
+ Definition: indicates that the regulator should be forced to a
particular mode, valid values are:
QCOM_RPM_FORCE_MODE_NONE - do not force any mode
QCOM_RPM_FORCE_MODE_LPM - force into low power mode
@@ -204,7 +204,7 @@ see regulator.txt - with additional custom properties described below:
- qcom,force-mode:
Usage: optional
Value type: <u32>
- Defintion: indicates that the regulator should not be forced to any
+ Definition: indicates that the regulator should not be forced to any
particular mode, valid values are:
QCOM_RPM_FORCE_MODE_NONE - do not force any mode
QCOM_RPM_FORCE_MODE_LPM - force into low power mode
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt b/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
index 0cb827b..3d965d5 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
+++ b/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
@@ -1,7 +1,7 @@
* The simple eMMC hardware reset provider
The purpose of this driver is to perform standard eMMC hw reset
-procedure, as descibed by Jedec 4.4 specification. This procedure is
+procedure, as described by Jedec 4.4 specification. This procedure is
performed just after MMC core enabled power to the given mmc host (to
fix possible issues if bootloader has left eMMC card in initialized or
unknown state), and before performing complete system reboot (also in
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
index c2546ce..0f6985b 100644
--- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
+++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
@@ -52,7 +52,7 @@ Optional properties:
v7.0. Use this property to describe the rare
earlier versions of this core that include WP
- -- Additonal SoC-specific NAND controller properties --
+ -- Additional SoC-specific NAND controller properties --
The NAND controller is integrated differently on the variety of SoCs on which it
is found. Part of this integration involves providing status and enable bits
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt | 2 +-
Documentation/devicetree/bindings/net/stmmac.txt | 4 ++--
Documentation/devicetree/bindings/net/ti,dp83867.txt | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt b/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
index e6a9d1c..e911a63 100644
--- a/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
+++ b/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
@@ -8,7 +8,7 @@ Required properties:
specifies a reference to the associating hardware driver node.
see Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt
- port-id: is the index of port provided by DSAF (the accelerator). DSAF can
- connect to 8 PHYs. Port 0 to 1 are both used for adminstration purpose. They
+ connect to 8 PHYs. Port 0 to 1 are both used for administration purpose. They
are called debug ports.
The remaining 6 PHYs are taken according to the mode of DSAF.
diff --git a/Documentation/devicetree/bindings/net/stmmac.txt b/Documentation/devicetree/bindings/net/stmmac.txt
index 6605d19..9651dfd 100644
--- a/Documentation/devicetree/bindings/net/stmmac.txt
+++ b/Documentation/devicetree/bindings/net/stmmac.txt
@@ -51,8 +51,8 @@ Optional properties:
AXI register inside the DMA module:
- snps,lpi_en: enable Low Power Interface
- snps,xit_frm: unlock on WoL
- - snps,wr_osr_lmt: max write oustanding req. limit
- - snps,rd_osr_lmt: max read oustanding req. limit
+ - snps,wr_osr_lmt: max write outstanding req. limit
+ - snps,rd_osr_lmt: max read outstanding req. limit
- snps,kbbe: do not cross 1KiB boundary.
- snps,axi_all: align address
- snps,blen: this is a vector of supported burst length.
diff --git a/Documentation/devicetree/bindings/net/ti,dp83867.txt b/Documentation/devicetree/bindings/net/ti,dp83867.txt
index 58d935b..5d21141 100644
--- a/Documentation/devicetree/bindings/net/ti,dp83867.txt
+++ b/Documentation/devicetree/bindings/net/ti,dp83867.txt
@@ -2,7 +2,7 @@
Required properties:
- reg - The ID number for the phy, usually a small integer
- - ti,rx-internal-delay - RGMII Recieve Clock Delay - see dt-bindings/net/ti-dp83867.h
+ - ti,rx-internal-delay - RGMII Receive Clock Delay - see dt-bindings/net/ti-dp83867.h
for applicable values
- ti,tx-internal-delay - RGMII Transmit Clock Delay - see dt-bindings/net/ti-dp83867.h
for applicable values
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
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>".
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
.../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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Reviewed-by: Steve French <[email protected]>
On Sun, Apr 24, 2016 at 7:24 PM, Eric Engestrom <[email protected]> wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thanks,
Steve
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
On 04/24/16 17:24, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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
On 25-04-16, 01:24, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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 <[email protected]>
--
viresh
On 04/24/16 17:24, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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
Signed-off-by: Eric Engestrom <[email protected]>
---
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 <[email protected]>
--------------
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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 <[email protected]> and others and additional patches
from Jamal <[email protected]>.
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
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/robust-futexes.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/robust-futexes.txt b/Documentation/robust-futexes.txt
index af6fce2..61c22d6 100644
--- a/Documentation/robust-futexes.txt
+++ b/Documentation/robust-futexes.txt
@@ -126,9 +126,9 @@ vma based method:
- no VM changes are needed - 'struct address_space' is left alone.
- - no registration of individual locks is needed: robust mutexes dont
+ - no registration of individual locks is needed: robust mutexes don't
need any extra per-lock syscalls. Robust mutexes thus become a very
- lightweight primitive - so they dont force the application designer
+ lightweight primitive - so they don't force the application designer
to do a hard choice between performance and robustness - robust
mutexes are just as fast.
@@ -202,7 +202,7 @@ and the remaining bits are for the TID.
Testing, architecture support
-----------------------------
-i've tested the new syscalls on x86 and x86_64, and have made sure the
+I've tested the new syscalls on x86 and x86_64, and have made sure the
parsing of the userspace list is robust [ ;-) ] even if the list is
deliberately corrupted.
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
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
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/scsi/ChangeLog.megaraid_sas | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/scsi/ChangeLog.megaraid_sas b/Documentation/scsi/ChangeLog.megaraid_sas
index 18b5709..20dcf20 100644
--- a/Documentation/scsi/ChangeLog.megaraid_sas
+++ b/Documentation/scsi/ChangeLog.megaraid_sas
@@ -63,7 +63,7 @@ Release Date : Sat. Feb 9, 2013 17:00:00 PST 2013 -
Current Version : 06.506.00.00-rc1
Old Version : 06.504.01.00-rc1
1. Add 4k FastPath DIF support.
- 2. Dont load DevHandle unless FastPath enabled.
+ 2. Don't load DevHandle unless FastPath enabled.
3. Version and Changelog update.
-------------------------------------------------------------------------------
Release Date : Mon. Oct 1, 2012 17:00:00 PST 2012 -
@@ -105,7 +105,7 @@ Old Version : 00.00.06.12-rc1
1. Fix reglockFlags for degraded raid5/6 for MR 9360/9380.
2. Mask off flags in ioctl path to prevent memory scribble with older
MegaCLI versions.
- 3. Remove poll_mode_io module paramater, sysfs node, and associated code.
+ 3. Remove poll_mode_io module parameter, sysfs node, and associated code.
-------------------------------------------------------------------------------
Release Date : Wed. Oct 5, 2011 17:00:00 PST 2010 -
(emaild-id:[email protected])
@@ -199,7 +199,7 @@ Old Version : 00.00.04.31-rc1
1. Add the Online Controller Reset (OCR) to the Driver.
OCR is the new feature for megaraid_sas driver which
will allow the fw to do the chip reset which will not
- affact the OS behavious.
+ affect the OS behavior.
To add the OCR support, driver need to do:
a). reset the controller chips -- Xscale and Gen2 which
@@ -233,7 +233,7 @@ Old Version : 00.00.04.31-rc1
failed state. Driver will kill adapter if can't bring back FW after the
this three times reset.
4. Add the input parameter max_sectors to 1MB support to our GEN2 controller.
- customer can use the input paramenter max_sectors to add 1MB support to GEN2
+ customer can use the input parameter max_sectors to add 1MB support to GEN2
controller.
1 Release Date : Thur. Oct 29, 2009 09:12:45 PST 2009 -
@@ -584,9 +584,9 @@ ii. Bug fix : Disable controller interrupt before firing INIT cmd to FW.
2 Current Version : 00.00.02.04
3 Older Version : 00.00.02.04
-i. Remove superflous instance_lock
+i. Remove superfluous instance_lock
- gets rid of the otherwise superflous instance_lock and avoids an unsave
+ gets rid of the otherwise superfluous instance_lock and avoids an unsafe
unsynchronized access in the error handler.
- Christoph Hellwig <[email protected]>
@@ -620,7 +620,7 @@ i. Register 16 byte CDB capability with scsi midlayer
3 Older Version : 00.00.02.01
i. New template defined to represent each family of controllers (identified by processor used).
- The template will have defintions that will be initialised to appropritae values for a specific family of controllers. The template definition has four function pointers. During driver initialisation the function pointers will be set based on the controller family type. This change is done to support new controllers that has different processors and thus different register set.
+ The template will have definitions that will be initialised to appropriate values for a specific family of controllers. The template definition has four function pointers. During driver initialisation the function pointers will be set based on the controller family type. This change is done to support new controllers that has different processors and thus different register set.
-Sumant Patro <[email protected]>
@@ -630,7 +630,7 @@ i. New template defined to represent each family of controllers (identified by p
i. Code reorganized to remove code duplication in megasas_build_cmd.
- "There's a lot of duplicate code megasas_build_cmd. Move that out of the different codepathes and merge the reminder of megasas_build_cmd into megasas_queue_command"
+ "There's a lot of duplicate code megasas_build_cmd. Move that out of the different codepaths and merge the reminder of megasas_build_cmd into megasas_queue_command"
- Christoph Hellwig <[email protected]>
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/sound/alsa/compress_offload.txt | 2 +-
Documentation/sound/alsa/soc/dapm.txt | 2 +-
Documentation/sound/alsa/soc/overview.txt | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/sound/alsa/compress_offload.txt b/Documentation/sound/alsa/compress_offload.txt
index 630c492..81476b4 100644
--- a/Documentation/sound/alsa/compress_offload.txt
+++ b/Documentation/sound/alsa/compress_offload.txt
@@ -149,7 +149,7 @@ Gapless Playback
================
When playing thru an album, the decoders have the ability to skip the encoder
delay and padding and directly move from one track content to another. The end
-user can perceive this as gapless playback as we dont have silence while
+user can perceive this as gapless playback as we don't have silence while
switching from one track to another
Also, there might be low-intensity noises due to encoding. Perfect gapless is
diff --git a/Documentation/sound/alsa/soc/dapm.txt b/Documentation/sound/alsa/soc/dapm.txt
index 6faab48..c45bd79 100644
--- a/Documentation/sound/alsa/soc/dapm.txt
+++ b/Documentation/sound/alsa/soc/dapm.txt
@@ -132,7 +132,7 @@ SOC_DAPM_SINGLE("HiFi Playback Switch", WM8731_APANA, 4, 1, 0),
SND_SOC_DAPM_MIXER("Output Mixer", WM8731_PWR, 4, 1, wm8731_output_mixer_controls,
ARRAY_SIZE(wm8731_output_mixer_controls)),
-If you dont want the mixer elements prefixed with the name of the mixer widget,
+If you don't want the mixer elements prefixed with the name of the mixer widget,
you can use SND_SOC_DAPM_MIXER_NAMED_CTL instead. the parameters are the same
as for SND_SOC_DAPM_MIXER.
diff --git a/Documentation/sound/alsa/soc/overview.txt b/Documentation/sound/alsa/soc/overview.txt
index ff88f52..f3f28b7 100644
--- a/Documentation/sound/alsa/soc/overview.txt
+++ b/Documentation/sound/alsa/soc/overview.txt
@@ -63,7 +63,7 @@ multiple re-usable component drivers :-
and any audio DSP drivers for that platform.
* Machine class driver: The machine driver class acts as the glue that
- decribes and binds the other component drivers together to form an ALSA
+ describes and binds the other component drivers together to form an ALSA
"sound card device". It handles any machine specific controls and
machine level audio events (e.g. turning on an amp at start of playback).
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/RCU/stallwarn.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RCU/stallwarn.txt b/Documentation/RCU/stallwarn.txt
index 0f7fb42..e93d041 100644
--- a/Documentation/RCU/stallwarn.txt
+++ b/Documentation/RCU/stallwarn.txt
@@ -49,7 +49,7 @@ rcupdate.rcu_task_stall_timeout
This boot/sysfs parameter controls the RCU-tasks stall warning
interval. A value of zero or less suppresses RCU-tasks stall
warnings. A positive value sets the stall-warning interval
- in jiffies. An RCU-tasks stall warning starts wtih the line:
+ in jiffies. An RCU-tasks stall warning starts with the line:
INFO: rcu_tasks detected stalls on tasks:
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/pps/pps.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt
index 7cb7264..50022b3 100644
--- a/Documentation/pps/pps.txt
+++ b/Documentation/pps/pps.txt
@@ -98,7 +98,7 @@ pps_source_info_s as follows:
};
and then calling the function pps_register_source() in your
-intialization routine as follows:
+initialization routine as follows:
source = pps_register_source(&pps_ktimer_info,
PPS_CAPTUREASSERT | PPS_OFFSETASSERT);
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/power/opp.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
index c6279c2..1721a86 100644
--- a/Documentation/power/opp.txt
+++ b/Documentation/power/opp.txt
@@ -146,7 +146,7 @@ dev_pm_opp_find_freq_exact - Search for an OPP based on an *exact* frequency and
rcu_read_lock();
opp = dev_pm_opp_find_freq_exact(dev, 1000000000, false);
rcu_read_unlock();
- /* dont operate on the pointer.. just do a sanity check.. */
+ /* don't operate on the pointer.. just do a sanity check.. */
if (IS_ERR(opp)) {
pr_err("frequency not disabled!\n");
/* trigger appropriate actions.. */
--
2.8.0
Signed-off-by: Eric Engestrom <[email protected]>
---
Documentation/lzo.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/lzo.txt b/Documentation/lzo.txt
index ea45dd3..285c54f 100644
--- a/Documentation/lzo.txt
+++ b/Documentation/lzo.txt
@@ -69,9 +69,9 @@ Description
IMPORTANT NOTE : in the code some length checks are missing because certain
instructions are called under the assumption that a certain number of bytes
- follow because it has already been garanteed before parsing the instructions.
+ follow because it has already been guaranteed before parsing the instructions.
They just have to "refill" this credit if they consume extra bytes. This is
- an implementation design choice independant on the algorithm or encoding.
+ an implementation design choice independent on the algorithm or encoding.
Byte sequences
--
2.8.0
On 25-04-16, 07:36, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> Documentation/power/opp.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
> index c6279c2..1721a86 100644
> --- a/Documentation/power/opp.txt
> +++ b/Documentation/power/opp.txt
> @@ -146,7 +146,7 @@ dev_pm_opp_find_freq_exact - Search for an OPP based on an *exact* frequency and
> rcu_read_lock();
> opp = dev_pm_opp_find_freq_exact(dev, 1000000000, false);
> rcu_read_unlock();
> - /* dont operate on the pointer.. just do a sanity check.. */
> + /* don't operate on the pointer.. just do a sanity check.. */
> if (IS_ERR(opp)) {
> pr_err("frequency not disabled!\n");
> /* trigger appropriate actions.. */
Acked-by: Viresh Kumar <[email protected]>
--
viresh
Le 25/04/2016 02:24, Eric Engestrom a ?crit :
> Signed-off-by: Eric Engestrom <[email protected]>
Hi,
thanks for the patch:
Acked-by: Nicolas Ferre <[email protected]>
> ---
> Documentation/arm/Atmel/README | 2 +-
> Documentation/arm/keystone/knav-qmss.txt | 2 +-
So, who will take care of this patch: can you carry it with you?
Jonathan may take it?
(As is touches other document, I can't take it with the Atmel/at91
material...)
Bye,
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/arm/Atmel/README b/Documentation/arm/Atmel/README
> index 0931cf7..adffac7 100644
> --- a/Documentation/arm/Atmel/README
> +++ b/Documentation/arm/Atmel/README
> @@ -16,7 +16,7 @@ git branches/tags and email subject always contain this "at91" sub-string.
>
> AT91 SoCs
> ---------
> -Documentation and detailled datasheet for each product are available on
> +Documentation and detailed datasheet for each product are available on
> the Atmel website: http://www.atmel.com.
>
> Flavors:
> diff --git a/Documentation/arm/keystone/knav-qmss.txt b/Documentation/arm/keystone/knav-qmss.txt
> index fcdb9fd..d15bf9a 100644
> --- a/Documentation/arm/keystone/knav-qmss.txt
> +++ b/Documentation/arm/keystone/knav-qmss.txt
> @@ -36,7 +36,7 @@ accumulator channels defined in DTS (example in DT documentation) to monitor
> CPPI/QMSS Low Level Driver document (docs/CPPI_QMSS_LLD_SDS.pdf) at
> git://git.ti.com/keystone-rtos/qmss-lld.git
>
> -k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
> +k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports up to 48 accumulator
> channels. This firmware is available under ti-keystone folder of
> firmware.git at
> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>
--
Nicolas Ferre
Am Montag, 25. April 2016, 01:24:06 schrieb Eric Engestrom:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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
For the Rockchip parts
Reviewed-by: Heiko Stuebner <[email protected]>
Hi,
It is required to write a commit message.
On 25/04/2016 at 01:24:00 +0100, Eric Engestrom wrote :
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> Documentation/arm/Atmel/README | 2 +-
> Documentation/arm/keystone/knav-qmss.txt | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/arm/Atmel/README b/Documentation/arm/Atmel/README
> index 0931cf7..adffac7 100644
> --- a/Documentation/arm/Atmel/README
> +++ b/Documentation/arm/Atmel/README
> @@ -16,7 +16,7 @@ git branches/tags and email subject always contain this "at91" sub-string.
>
> AT91 SoCs
> ---------
> -Documentation and detailled datasheet for each product are available on
> +Documentation and detailed datasheet for each product are available on
> the Atmel website: http://www.atmel.com.
>
> Flavors:
> diff --git a/Documentation/arm/keystone/knav-qmss.txt b/Documentation/arm/keystone/knav-qmss.txt
> index fcdb9fd..d15bf9a 100644
> --- a/Documentation/arm/keystone/knav-qmss.txt
> +++ b/Documentation/arm/keystone/knav-qmss.txt
> @@ -36,7 +36,7 @@ accumulator channels defined in DTS (example in DT documentation) to monitor
> CPPI/QMSS Low Level Driver document (docs/CPPI_QMSS_LLD_SDS.pdf) at
> git://git.ti.com/keystone-rtos/qmss-lld.git
>
> -k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
> +k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports up to 48 accumulator
> channels. This firmware is available under ti-keystone folder of
> firmware.git at
> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> --
> 2.8.0
>
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
On Mon, Apr 25, 2016 at 07:36:59AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Good catch.
Reviewed-by: Josh Triplett <[email protected]>
> ---
> Documentation/RCU/stallwarn.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/stallwarn.txt b/Documentation/RCU/stallwarn.txt
> index 0f7fb42..e93d041 100644
> --- a/Documentation/RCU/stallwarn.txt
> +++ b/Documentation/RCU/stallwarn.txt
> @@ -49,7 +49,7 @@ rcupdate.rcu_task_stall_timeout
> This boot/sysfs parameter controls the RCU-tasks stall warning
> interval. A value of zero or less suppresses RCU-tasks stall
> warnings. A positive value sets the stall-warning interval
> - in jiffies. An RCU-tasks stall warning starts wtih the line:
> + in jiffies. An RCU-tasks stall warning starts with the line:
>
> INFO: rcu_tasks detected stalls on tasks:
>
> --
> 2.8.0
>
On Mon, 25 Apr 2016 08:37:02 +0200,
Eric Engestrom wrote:
>
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Takashi
On Monday 25 April 2016 05:54 AM, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Thx Eric.
Applied to ARC for-curr !
-Vineet
On Mon, Apr 25, 2016 at 07:37:02AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> Documentation/sound/alsa/compress_offload.txt | 2 +-
Acked-by: Vinod Koul <[email protected]>
Thanks
--
~Vinod
On Mon, 25 Apr 2016 07:37:04 +0100
Eric Engestrom <[email protected]> wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> 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;
Acked-by: Cornelia Huck <[email protected]>
Paolo/Radim, will you take this through the kvm tree directly?
On Mon, Apr 25, 2016 at 01:24:05AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/arm/cci.txt | 2 +-
> Documentation/devicetree/bindings/arm/spear-misc.txt | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/cci.txt b/Documentation/devicetree/bindings/arm/cci.txt
> index a1a5a7e..0f2153e 100644
> --- a/Documentation/devicetree/bindings/arm/cci.txt
> +++ b/Documentation/devicetree/bindings/arm/cci.txt
> @@ -100,7 +100,7 @@ specific to ARM.
> "arm,cci-400-pmu,r0"
> "arm,cci-400-pmu,r1"
> "arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
> - secure acces to CCI registers
> + secure access to CCI registers
> "arm,cci-500-pmu,r0"
> "arm,cci-550-pmu,r0"
> - reg:
> diff --git a/Documentation/devicetree/bindings/arm/spear-misc.txt b/Documentation/devicetree/bindings/arm/spear-misc.txt
> index cf64982..e404e25 100644
> --- a/Documentation/devicetree/bindings/arm/spear-misc.txt
> +++ b/Documentation/devicetree/bindings/arm/spear-misc.txt
> @@ -6,4 +6,4 @@ few properties of different peripheral controllers.
> misc node required properties:
>
> - compatible Should be "st,spear1340-misc", "syscon".
> -- reg: Address range of misc space upto 8K
> +- reg: Address range of misc space up to 8K
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:07AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt b/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
> index 22756b3..a782659 100644
> --- a/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
> +++ b/Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
> @@ -41,7 +41,7 @@ Video interfaces:
> endpoint node connected from mic node (reg = 0):
> - remote-endpoint: specifies the endpoint in mic node. This node is required
> for Exynos5433 mipi dsi. So mic can access to panel node
> - thoughout this dsi node.
> + throughout this dsi node.
> endpoint node connected to panel node (reg = 1):
> - remote-endpoint: specifies the endpoint in panel node. This node is
> required in all kinds of exynos mipi dsi to represent
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:08AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt b/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
> index 2291c40..3cf0072d 100644
> --- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
> +++ b/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
> @@ -7,7 +7,7 @@ Required properties:
> - compatible: Should be "xlnx,axi-dma-1.00.a"
> - #dma-cells: Should be <1>, see "dmas" property below
> - reg: Should contain DMA registers location and length.
> -- dma-channel child node: Should have atleast one channel and can have upto
> +- dma-channel child node: Should have at least one channel and can have up to
> two channels per device. This node specifies the properties of each
> DMA channel (see child node properties below).
>
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:09AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/input/ads7846.txt | 2 +-
> Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/ads7846.txt b/Documentation/devicetree/bindings/input/ads7846.txt
> index c6cfe2e..9fc47b0 100644
> --- a/Documentation/devicetree/bindings/input/ads7846.txt
> +++ b/Documentation/devicetree/bindings/input/ads7846.txt
> @@ -29,7 +29,7 @@ Optional properties:
> ti,vref-delay-usecs vref supply delay in usecs, 0 for
> external vref (u16).
> ti,vref-mv The VREF voltage, in millivolts (u16).
> - Set to 0 to use internal refernce
> + Set to 0 to use internal references
> (ADS7846).
> ti,keep-vref-on set to keep vref on for differential
> measurements as well
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt b/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
> index cdf05f9..abfcab3 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
> +++ b/Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt
> @@ -15,7 +15,7 @@ Optional properties:
> - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
> - fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
> between 1 and 4096. It is the ratio between the internal reference voltage
> - and the measured voltage after the plate was precharged. Resistence between
> + and the measured voltage after the plate was precharged. Resistance between
> plates and therefore the voltage decreases with pressure so that a smaller
> value is equivalent to a higher pressure.
> - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:10AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> .../devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
> index 43effa0..18d4f40 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
> +++ b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
> @@ -4,7 +4,7 @@ All TI OMAP4/5 (and their derivatives) an interrupt controller that
> routes interrupts to the GIC, and also serves as a wakeup source. It
> is also referred to as "WUGEN-MPU", hence the name of the binding.
>
> -Reguired properties:
> +Required properties:
>
> - compatible : should contain at least "ti,omap4-wugen-mpu" or
> "ti,omap5-wugen-mpu"
> @@ -20,7 +20,7 @@ Notes:
> - Because this HW ultimately routes interrupts to the GIC, the
> interrupt specifier must be that of the GIC.
> - Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
> - are explicitly forbiden.
> + are explicitly forbidden.
>
> Example:
>
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:11AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/media/xilinx/video.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/media/xilinx/video.txt b/Documentation/devicetree/bindings/media/xilinx/video.txt
> index cbd46fa..68ac210 100644
> --- a/Documentation/devicetree/bindings/media/xilinx/video.txt
> +++ b/Documentation/devicetree/bindings/media/xilinx/video.txt
> @@ -20,7 +20,7 @@ The following properties are common to all Xilinx video IP cores.
> - xlnx,video-format: This property represents a video format transmitted on an
> AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
> Video IP and System Design Guide" [UG934]. How the format relates to the IP
> - core is decribed in the IP core bindings documentation.
> + core is described in the IP core bindings documentation.
>
> - xlnx,video-width: This property qualifies the video format with the sample
> width expressed as a number of bits per pixel component. All components must
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> index 5e97a95..b98b291 100644
> --- a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> +++ b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> @@ -178,7 +178,7 @@ see regulator.txt - with additional custom properties described below:
> - qcom,force-mode:
> Usage: optional (default if no other qcom,force-mode is specified)
> Value type: <u32>
> - Defintion: indicates that the regulator should be forced to a
> + Definition: indicates that the regulator should be forced to a
> particular mode, valid values are:
> QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> QCOM_RPM_FORCE_MODE_LPM - force into low power mode
> @@ -204,7 +204,7 @@ see regulator.txt - with additional custom properties described below:
> - qcom,force-mode:
> Usage: optional
> Value type: <u32>
> - Defintion: indicates that the regulator should not be forced to any
> + Definition: indicates that the regulator should not be forced to any
> particular mode, valid values are:
> QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> QCOM_RPM_FORCE_MODE_LPM - force into low power mode
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:13AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt b/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
> index 0cb827b..3d965d5 100644
> --- a/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
> +++ b/Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.txt
> @@ -1,7 +1,7 @@
> * The simple eMMC hardware reset provider
>
> The purpose of this driver is to perform standard eMMC hw reset
> -procedure, as descibed by Jedec 4.4 specification. This procedure is
> +procedure, as described by Jedec 4.4 specification. This procedure is
> performed just after MMC core enabled power to the given mmc host (to
> fix possible issues if bootloader has left eMMC card in initialized or
> unknown state), and before performing complete system reboot (also in
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:14AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
> index c2546ce..0f6985b 100644
> --- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
> +++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
> @@ -52,7 +52,7 @@ Optional properties:
> v7.0. Use this property to describe the rare
> earlier versions of this core that include WP
>
> - -- Additonal SoC-specific NAND controller properties --
> + -- Additional SoC-specific NAND controller properties --
>
> The NAND controller is integrated differently on the variety of SoCs on which it
> is found. Part of this integration involves providing status and enable bits
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:15AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt | 2 +-
> Documentation/devicetree/bindings/net/stmmac.txt | 4 ++--
> Documentation/devicetree/bindings/net/ti,dp83867.txt | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt b/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
> index e6a9d1c..e911a63 100644
> --- a/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
> +++ b/Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt
> @@ -8,7 +8,7 @@ Required properties:
> specifies a reference to the associating hardware driver node.
> see Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt
> - port-id: is the index of port provided by DSAF (the accelerator). DSAF can
> - connect to 8 PHYs. Port 0 to 1 are both used for adminstration purpose. They
> + connect to 8 PHYs. Port 0 to 1 are both used for administration purpose. They
> are called debug ports.
>
> The remaining 6 PHYs are taken according to the mode of DSAF.
> diff --git a/Documentation/devicetree/bindings/net/stmmac.txt b/Documentation/devicetree/bindings/net/stmmac.txt
> index 6605d19..9651dfd 100644
> --- a/Documentation/devicetree/bindings/net/stmmac.txt
> +++ b/Documentation/devicetree/bindings/net/stmmac.txt
> @@ -51,8 +51,8 @@ Optional properties:
> AXI register inside the DMA module:
> - snps,lpi_en: enable Low Power Interface
> - snps,xit_frm: unlock on WoL
> - - snps,wr_osr_lmt: max write oustanding req. limit
> - - snps,rd_osr_lmt: max read oustanding req. limit
> + - snps,wr_osr_lmt: max write outstanding req. limit
> + - snps,rd_osr_lmt: max read outstanding req. limit
> - snps,kbbe: do not cross 1KiB boundary.
> - snps,axi_all: align address
> - snps,blen: this is a vector of supported burst length.
> diff --git a/Documentation/devicetree/bindings/net/ti,dp83867.txt b/Documentation/devicetree/bindings/net/ti,dp83867.txt
> index 58d935b..5d21141 100644
> --- a/Documentation/devicetree/bindings/net/ti,dp83867.txt
> +++ b/Documentation/devicetree/bindings/net/ti,dp83867.txt
> @@ -2,7 +2,7 @@
>
> Required properties:
> - reg - The ID number for the phy, usually a small integer
> - - ti,rx-internal-delay - RGMII Recieve Clock Delay - see dt-bindings/net/ti-dp83867.h
> + - ti,rx-internal-delay - RGMII Receive Clock Delay - see dt-bindings/net/ti-dp83867.h
> for applicable values
> - ti,tx-internal-delay - RGMII Transmit Clock Delay - see dt-bindings/net/ti-dp83867.h
> for applicable values
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:16AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> 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>".
>
> --
> 2.8.0
>
On Mon, Apr 25, 2016 at 01:24:17AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> 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
>
On Mon, Apr 25, 2016 at 01:24:18AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> 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
>
On Mon, Apr 25, 2016 at 01:24:19AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
Applied, thanks.
Rob
> ---
> .../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
>
On Sun, Apr 24, 2016 at 7:24 PM, Eric Engestrom <[email protected]> wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
Applied with Randy's fix.
Rob
2016-04-25 14:00+0200, Cornelia Huck:
> On Mon, 25 Apr 2016 07:37:04 +0100
> Eric Engestrom <[email protected]> wrote:
>> Signed-off-by: Eric Engestrom <[email protected]>
>> ---
>> 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;
>
> Acked-by: Cornelia Huck <[email protected]>
>
> Paolo/Radim, will you take this through the kvm tree directly?
Ok, I have queued it, thanks.
On Mon, 25 Apr 2016, Rob Herring wrote:
> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> > Signed-off-by: Eric Engestrom <[email protected]>
>
> Applied, thanks.
I'd prefer to continue taking these if you don't mind Rob. It'd limit
on the amount of immutable branch pull requests I have to send/handle.
> > ---
> > Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > index 5e97a95..b98b291 100644
> > --- a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > +++ b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > @@ -178,7 +178,7 @@ see regulator.txt - with additional custom properties described below:
> > - qcom,force-mode:
> > Usage: optional (default if no other qcom,force-mode is specified)
> > Value type: <u32>
> > - Defintion: indicates that the regulator should be forced to a
> > + Definition: indicates that the regulator should be forced to a
> > particular mode, valid values are:
> > QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> > QCOM_RPM_FORCE_MODE_LPM - force into low power mode
> > @@ -204,7 +204,7 @@ see regulator.txt - with additional custom properties described below:
> > - qcom,force-mode:
> > Usage: optional
> > Value type: <u32>
> > - Defintion: indicates that the regulator should not be forced to any
> > + Definition: indicates that the regulator should not be forced to any
> > particular mode, valid values are:
> > QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> > QCOM_RPM_FORCE_MODE_LPM - force into low power mode
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
On Mon, Apr 25, 2016 at 12:48:13AM -0700, Josh Triplett wrote:
> On Mon, Apr 25, 2016 at 07:36:59AM +0100, Eric Engestrom wrote:
> > Signed-off-by: Eric Engestrom <[email protected]>
>
> Good catch.
>
> Reviewed-by: Josh Triplett <[email protected]>
Queued, thank you both!
Thanx, Paul
> > ---
> > Documentation/RCU/stallwarn.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/RCU/stallwarn.txt b/Documentation/RCU/stallwarn.txt
> > index 0f7fb42..e93d041 100644
> > --- a/Documentation/RCU/stallwarn.txt
> > +++ b/Documentation/RCU/stallwarn.txt
> > @@ -49,7 +49,7 @@ rcupdate.rcu_task_stall_timeout
> > This boot/sysfs parameter controls the RCU-tasks stall warning
> > interval. A value of zero or less suppresses RCU-tasks stall
> > warnings. A positive value sets the stall-warning interval
> > - in jiffies. An RCU-tasks stall warning starts wtih the line:
> > + in jiffies. An RCU-tasks stall warning starts with the line:
> >
> > INFO: rcu_tasks detected stalls on tasks:
> >
> > --
> > 2.8.0
> >
>
On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[email protected]> wrote:
> On Mon, 25 Apr 2016, Rob Herring wrote:
>
>> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
>> > Signed-off-by: Eric Engestrom <[email protected]>
>>
>> Applied, thanks.
>
> I'd prefer to continue taking these if you don't mind Rob. It'd limit
> on the amount of immutable branch pull requests I have to send/handle.
Why? Do you really expect to have a dependency here?
Rob
On 24 April 2016 at 18:23, Eric Engestrom <[email protected]> wrote:
> Signed-off-by: Eric Engestrom <[email protected]>
> ---
> Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x | 2 +-
> Documentation/ABI/testing/sysfs-bus-event_source-devices-events | 4 ++--
> Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 | 2 +-
> Documentation/ABI/testing/sysfs-driver-tegra-fuse | 2 +-
> Documentation/ABI/testing/sysfs-fs-xfs | 2 +-
> 5 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
> index 2355ed8..19b83f4 100644
> --- a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
> +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
> @@ -378,7 +378,7 @@ Date: April 2015
> KernelVersion: 4.01
> Contact: Mathieu Poirier <[email protected]>
> Description: (R) Returns the maximum size of the data value, data address,
> - VMID, context ID and instuction address in the trace unit
> + VMID, context ID and instruction address in the trace unit
> (0x1E8). The value is taken directly from the HW.
For this part: Acked-by: Mathieu Poirier <[email protected]>
>
> What: /sys/bus/coresight/devices/<memory_map>.etm/trcidr/trcidr3
> diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
> index 505f080..77de58d 100644
> --- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
> +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
> @@ -47,7 +47,7 @@ Description: Per-pmu performance monitoring events specific to the running syste
> If a <term> is specified alone (without an assigned value), it
> is implied that 0x1 is assigned to that <term>.
>
> - Examples (each of these lines would be in a seperate file):
> + Examples (each of these lines would be in a separate file):
>
> event=0x2abc
> event=0x423,inv,cmask=0x3
> @@ -83,7 +83,7 @@ Description: Perf event scaling factors
>
> A string representing a floating point value expressed in
> scientific notation to be multiplied by the event count
> - recieved from the kernel to match the unit specified in the
> + received from the kernel to match the unit specified in the
> <event>.unit file.
>
> Example:
> diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
> index f893337..ec27c6c 100644
> --- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
> +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
> @@ -4,7 +4,7 @@ Contact: Linux on PowerPC Developer List <[email protected]>
> Description:
> Provides access to the binary "24x7 catalog" provided by the
> hypervisor on POWER7 and 8 systems. This catalog lists events
> - avaliable from the powerpc "hv_24x7" pmu. Its format is
> + available from the powerpc "hv_24x7" pmu. Its format is
> documented here:
> https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h
>
> diff --git a/Documentation/ABI/testing/sysfs-driver-tegra-fuse b/Documentation/ABI/testing/sysfs-driver-tegra-fuse
> index 69f5af6..b8936fa 100644
> --- a/Documentation/ABI/testing/sysfs-driver-tegra-fuse
> +++ b/Documentation/ABI/testing/sysfs-driver-tegra-fuse
> @@ -3,7 +3,7 @@ Date: February 2014
> Contact: Peter De Schrijver <[email protected]>
> Description: read-only access to the efuses on Tegra20, Tegra30, Tegra114
> and Tegra124 SoC's from NVIDIA. The efuses contain write once
> - data programmed at the factory. The data is layed out in 32bit
> + data programmed at the factory. The data is laid out in 32bit
> words in LSB first format. Each bit represents a single value
> as decoded from the fuse registers. Bits order/assignment
> exactly matches the HW registers, including any unused bits.
> diff --git a/Documentation/ABI/testing/sysfs-fs-xfs b/Documentation/ABI/testing/sysfs-fs-xfs
> index ea0cc8c..f704925 100644
> --- a/Documentation/ABI/testing/sysfs-fs-xfs
> +++ b/Documentation/ABI/testing/sysfs-fs-xfs
> @@ -33,7 +33,7 @@ Contact: [email protected]
> Description:
> The current state of the log write grant head. It
> represents the total log reservation of all currently
> - oustanding transactions, including regrants due to
> + outstanding transactions, including regrants due to
> rolling transactions. The grant head is exported in
> "cycle:bytes" format.
> Users: xfstests
> --
> 2.8.0
>
On Mon, 25 Apr 2016, Rob Herring wrote:
> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[email protected]> wrote:
> > On Mon, 25 Apr 2016, Rob Herring wrote:
> >
> >> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> >> > Signed-off-by: Eric Engestrom <[email protected]>
> >>
> >> Applied, thanks.
> >
> > I'd prefer to continue taking these if you don't mind Rob. It'd limit
> > on the amount of immutable branch pull requests I have to send/handle.
>
> Why? Do you really expect to have a dependency here?
Because the file is in ".*/mfd/.*", which normally goes through the MFD
tree.
$ git log --committer="Rob Herring" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
6
$ git log --committer="Lee Jones" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
99
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
On Tue, Apr 26, 2016 at 1:35 AM, Lee Jones <[email protected]> wrote:
> On Mon, 25 Apr 2016, Rob Herring wrote:
>
>> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[email protected]> wrote:
>> > On Mon, 25 Apr 2016, Rob Herring wrote:
>> >
>> >> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
>> >> > Signed-off-by: Eric Engestrom <[email protected]>
>> >>
>> >> Applied, thanks.
>> >
>> > I'd prefer to continue taking these if you don't mind Rob. It'd limit
>> > on the amount of immutable branch pull requests I have to send/handle.
>>
>> Why? Do you really expect to have a dependency here?
>
> Because the file is in ".*/mfd/.*", which normally goes through the MFD
> tree.
>
> $ git log --committer="Rob Herring" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> 6
> $ git log --committer="Lee Jones" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> 99
That is because most changes are coupled with drivers. For changes
that are standalone without any dependency, they go thru my tree. If
we're getting any merge conflicts beyond which Linus can/wants to fix,
then there is a problem because bindings shouldn't be changing that
much.
Eventually, I think we need to merge all the bindings thru a single
tree. Otherwise, we'll never move toward moving bindings out of the
kernel (unless we just sync from the kernel tree to a standalone
repo).
Rob
On Tue, 26 Apr 2016, Rob Herring wrote:
> On Tue, Apr 26, 2016 at 1:35 AM, Lee Jones <[email protected]> wrote:
> > On Mon, 25 Apr 2016, Rob Herring wrote:
> >
> >> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[email protected]> wrote:
> >> > On Mon, 25 Apr 2016, Rob Herring wrote:
> >> >
> >> >> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> >> >> > Signed-off-by: Eric Engestrom <[email protected]>
> >> >>
> >> >> Applied, thanks.
> >> >
> >> > I'd prefer to continue taking these if you don't mind Rob. It'd limit
> >> > on the amount of immutable branch pull requests I have to send/handle.
> >>
> >> Why? Do you really expect to have a dependency here?
> >
> > Because the file is in ".*/mfd/.*", which normally goes through the MFD
> > tree.
> >
> > $ git log --committer="Rob Herring" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> > 6
> > $ git log --committer="Lee Jones" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> > 99
>
> That is because most changes are coupled with drivers. For changes
> that are standalone without any dependency, they go thru my tree. If
> we're getting any merge conflicts beyond which Linus can/wants to fix,
> then there is a problem because bindings shouldn't be changing that
> much.
That's certainly the first I've heard about it. It makes far less
sense for changes pertaining to a single directory to go in via 2
separate trees. IMO that's asking for trouble.
> Eventually, I think we need to merge all the bindings thru a single
> tree. Otherwise, we'll never move toward moving bindings out of the
> kernel (unless we just sync from the kernel tree to a standalone
> repo).
Once (if they ever) move out from the kernel tree, then I agree with
you, they should be dealt with as completely separate entities and be
merged though different trees, but until then we need to make a
decision; either you take them all or I take them all. I thought we
were doing the latter already.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Commit-ID: 1d4093d3b3a70b947822cca76d6e4132767ce089
Gitweb: http://git.kernel.org/tip/1d4093d3b3a70b947822cca76d6e4132767ce089
Author: Eric Engestrom <[email protected]>
AuthorDate: Mon, 25 Apr 2016 07:36:54 +0100
Committer: Ingo Molnar <[email protected]>
CommitDate: Thu, 28 Apr 2016 10:40:57 +0200
locking/Documentation/lockdep: Fix spelling mistakes
Signed-off-by: Eric Engestrom <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
---
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:
----------------
On Mon, 25 Apr 2016 07:36:53 +0100
Eric Engestrom <[email protected]> wrote:
> -laptops, being called "Toshiba HDD Protection - Shock Sensor" officialy,
> +laptops, being called "Toshiba HDD Protection - Shock Sensor" officially,
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:36:55 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/lzo.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:36:58 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/pps/pps.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:36:58 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/pps/pps.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:37:00 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/robust-futexes.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:37:01 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/scsi/ChangeLog.megaraid_sas | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
Applied to the docs tree (after fixing trailing whitespace errors - the
new and the old ones).
jon
On Mon, 25 Apr 2016 07:37:05 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/vm/transhuge.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:37:06 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/x86/intel_mpx.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied to the docs tree, thanks.
jon
On Mon, 25 Apr 2016 07:37:07 +0100
Eric Engestrom <[email protected]> wrote:
> Documentation/xillybus.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to the docs tree, thanks.
jon
On Thu, 28 Apr 2016 07:31:43 -0600
Jonathan Corbet <[email protected]> wrote:
> On Mon, 25 Apr 2016 07:37:05 +0100
> Eric Engestrom <[email protected]> wrote:
>
> > Documentation/vm/transhuge.txt | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Applied to the docs tree, thanks.
Actually, I've just unapplied this one; it conflicts against changes in
Andrew's tree and, thus, linux-next. Andrew, maybe you'd like to take it
on top of what you have now?
jon
From: Eric Engestrom <[email protected]>
Date: Mon, 25 Apr 2016 07:36:56 +0100
> Signed-off-by: Eric Engestrom <[email protected]>
Applied.
On Thu, 28 Apr 2016 07:46:07 -0600 Jonathan Corbet <[email protected]> wrote:
> On Thu, 28 Apr 2016 07:31:43 -0600
> Jonathan Corbet <[email protected]> wrote:
>
> > On Mon, 25 Apr 2016 07:37:05 +0100
> > Eric Engestrom <[email protected]> wrote:
> >
> > > Documentation/vm/transhuge.txt | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > Applied to the docs tree, thanks.
>
> Actually, I've just unapplied this one; it conflicts against changes in
> Andrew's tree and, thus, linux-next. Andrew, maybe you'd like to take it
> on top of what you have now?
Sure.
That Documentation/vm/transhuge.txt paragraph isn't in great shape so
I gave it some extra help.
From: Eric Engestrom <[email protected]>
Subject: Documentation: vm: fix spelling mistakes
Signed-off-by: Eric Engestrom <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---
Documentation/vm/transhuge.txt | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff -puN Documentation/vm/transhuge.txt~documentation-vm-fix-spelling-mistakes Documentation/vm/transhuge.txt
--- a/Documentation/vm/transhuge.txt~documentation-vm-fix-spelling-mistakes
+++ a/Documentation/vm/transhuge.txt
@@ -340,7 +340,7 @@ unaffected. libhugetlbfs will also work
== 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 ->_ma
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
@@ -432,10 +432,10 @@ page->_mapcount.
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 ->_refcount until atomic_add(). It prevent scanner
-from geting reference to tail page up to the point. After the atomic_add()
-we don't care about ->_refcount value. We already known how many references
-with should uncharge from head page.
+All tail pages have zero ->_refcount until atomic_add(). This prevents the
+scanner from getting a reference to the tail page up to that point. After the
+atomic_add() we don't care about the ->_refcount value. We already known how
+many references should be uncharged from the head page.
For head page get_page_unless_zero() will succeed and we don't mind. It's
clear where reference should go after split: it will stay on head page.
_