[PATCH 00/41] Documentation: fix spelling mistakes

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

Re: [PATCH 13/41] Documentation: dt: interrupt-controller: fix spelling mistakes

Rob Herring-3
On Mon, Apr 25, 2016 at 01:24:10AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 14/41] Documentation: dt: media: fix spelling mistake

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:11AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 16/41] Documentation: dt: mmc: fix spelling mistake

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:13AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 17/41] Documentation: dt: mtd: fix spelling mistake

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:14AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 18/41] Documentation: dt: net: fix spelling mistakes

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:15AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

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

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:16AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

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

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:17AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

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

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:18AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

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

Rob Herring-3
In reply to this post by Eric Engestrom-2
On Mon, Apr 25, 2016 at 01:24:19AM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>

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
>
Reply | Threaded
Open this post in threaded view
|

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

Rob Herring-5
In reply to this post by Eric Engestrom-2
On Sun, Apr 24, 2016 at 7:24 PM, Eric Engestrom <[hidden email]> wrote:
> Signed-off-by: Eric Engestrom <[hidden email]>
> ---

Applied with Randy's fix.

Rob
Reply | Threaded
Open this post in threaded view
|

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

Radim Krčmář
In reply to this post by Cornelia Huck-4
2016-04-25 14:00+0200, Cornelia Huck:

> On Mon, 25 Apr 2016 07:37:04 +0100
> Eric Engestrom <[hidden email]> wrote:
>> Signed-off-by: Eric Engestrom <[hidden email]>
>> ---
>>  Documentation/virtual/kvm/devices/s390_flic.txt | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/virtual/kvm/devices/s390_flic.txt b/Documentation/virtual/kvm/devices/s390_flic.txt
>> index e3e314c..13a1261 100644
>> --- a/Documentation/virtual/kvm/devices/s390_flic.txt
>> +++ b/Documentation/virtual/kvm/devices/s390_flic.txt
>> @@ -68,7 +68,7 @@ struct kvm_s390_io_adapter {
>>
>>    KVM_DEV_FLIC_ADAPTER_MODIFY
>>      Modifies attributes of an existing I/O adapter interrupt source. Takes
>> -    a kvm_s390_io_adapter_req specifiying the adapter and the operation:
>> +    a kvm_s390_io_adapter_req specifying the adapter and the operation:
>>
>>  struct kvm_s390_io_adapter_req {
>>   __u32 id;
>
> Acked-by: Cornelia Huck <[hidden email]>
>
> Paolo/Radim, will you take this through the kvm tree directly?

Ok, I have queued it, thanks.
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Lee Jones
In reply to this post by Rob Herring-3
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 <[hidden email]>
>
> 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
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 33/41] Documentation: RCU: fix spelling mistake

Paul E. McKenney
In reply to this post by Josh Triplett
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 <[hidden email]>
>
> Good catch.
>
> Reviewed-by: Josh Triplett <[hidden email]>

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
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Rob Herring-3
In reply to this post by Lee Jones
On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[hidden email]> 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 <[hidden email]>
>>
>> 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
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 02/41] Documentation: sysfs: fix spelling mistakes

Mathieu Poirier
In reply to this post by Eric Engestrom-2
On 24 April 2016 at 18:23, Eric Engestrom <[hidden email]> wrote:

> Signed-off-by: Eric Engestrom <[hidden email]>
> ---
>  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 <[hidden email]>
>  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 <[hidden email]>

>
>  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 <[hidden email]>
>  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 <[hidden email]>
>  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:      [hidden email]
>  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
>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Lee Jones
In reply to this post by Rob Herring-3
On Mon, 25 Apr 2016, Rob Herring wrote:

> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[hidden email]> 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 <[hidden email]>
> >>
> >> 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
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Rob Herring-3
On Tue, Apr 26, 2016 at 1:35 AM, Lee Jones <[hidden email]> wrote:

> On Mon, 25 Apr 2016, Rob Herring wrote:
>
>> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[hidden email]> 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 <[hidden email]>
>> >>
>> >> 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
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

Lee Jones
On Tue, 26 Apr 2016, Rob Herring wrote:

> On Tue, Apr 26, 2016 at 1:35 AM, Lee Jones <[hidden email]> wrote:
> > On Mon, 25 Apr 2016, Rob Herring wrote:
> >
> >> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <[hidden email]> 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 <[hidden email]>
> >> >>
> >> >> 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
Reply | Threaded
Open this post in threaded view
|

[tip:locking/core] locking/Documentation/lockdep: Fix spelling mistakes

tip-bot for Peter Zijlstra
In reply to this post by Eric Engestrom-2
Commit-ID:  1d4093d3b3a70b947822cca76d6e4132767ce089
Gitweb:     http://git.kernel.org/tip/1d4093d3b3a70b947822cca76d6e4132767ce089
Author:     Eric Engestrom <[hidden email]>
AuthorDate: Mon, 25 Apr 2016 07:36:54 +0100
Committer:  Ingo Molnar <[hidden email]>
CommitDate: Thu, 28 Apr 2016 10:40:57 +0200

locking/Documentation/lockdep: Fix spelling mistakes

Signed-off-by: Eric Engestrom <[hidden email]>
Signed-off-by: Peter Zijlstra (Intel) <[hidden email]>
Cc: Jonathan Corbet <[hidden email]>
Cc: Linus Torvalds <[hidden email]>
Cc: Peter Zijlstra <[hidden email]>
Cc: Thomas Gleixner <[hidden email]>
Link: http://lkml.kernel.org/r/1461566229-4717-2-git-send-email-eric@...
Signed-off-by: Ingo Molnar <[hidden email]>
---
 Documentation/locking/lockdep-design.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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