Re: [PATCH] Documentation: dt-bindings: Fix interrupt documentation file path

[Lee Jones]

On Mon, 21 Sep 2015, Andrew F. Davis wrote:

> Fix the incorrect interrupt documentation file path in binding docs.
> 
> Signed-off-by: Andrew F. Davis <afd@xxxxxx>
> ---
>  Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt | 2 +-
>  Documentation/devicetree/bindings/mfd/arizona.txt          | 2 +-
>  Documentation/devicetree/bindings/mfd/palmas.txt           | 2 +-

Acked-by: Lee Jones <lee.jones@xxxxxxxxxx>

>  Documentation/devicetree/bindings/sound/wm8994.txt         | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt b/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> index dd5d2c0..4d6c8cd 100644
> --- a/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> @@ -24,7 +24,7 @@ controller.
>  - #interrupt-cells : Specifies the number of cells needed to encode an
>    interrupt.  Shall be set to 2.  The first cell defines the interrupt number,
>    the second encodes the triger flags encoded as described in
> -  Documentation/devicetree/bindings/interrupts.txt
> +  Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>  - interrupt-parent : The parent interrupt controller.
>  - interrupts : The interrupt to the parent controller raised when GPIOs
>    generate the interrupts.
> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> index a8fee60..3d361ec 100644
> --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> @@ -24,7 +24,7 @@ Required properties:
>    - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
>      The first cell is the IRQ number.
>      The second cell is the flags, encoded as the trigger masks from
> -    Documentation/devicetree/bindings/interrupts.txt
> +    Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>  
>    - gpio-controller : Indicates this device is a GPIO controller.
>    - #gpio-cells : Must be 2. The first cell is the pin number and the
> diff --git a/Documentation/devicetree/bindings/mfd/palmas.txt b/Documentation/devicetree/bindings/mfd/palmas.txt
> index eda8989..8ae1a32 100644
> --- a/Documentation/devicetree/bindings/mfd/palmas.txt
> +++ b/Documentation/devicetree/bindings/mfd/palmas.txt
> @@ -24,7 +24,7 @@ and also the generic series names
>  - #interrupt-cells : should be set to 2 for IRQ number and flags
>    The first cell is the IRQ number.
>    The second cell is the flags, encoded as the trigger masks from
> -  Documentation/devicetree/bindings/interrupts.txt
> +  Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>  - interrupt-parent : The parent interrupt controller.
>  
>  Optional properties:
> diff --git a/Documentation/devicetree/bindings/sound/wm8994.txt b/Documentation/devicetree/bindings/sound/wm8994.txt
> index e045e90..68c4e8d 100644
> --- a/Documentation/devicetree/bindings/sound/wm8994.txt
> +++ b/Documentation/devicetree/bindings/sound/wm8994.txt
> @@ -30,7 +30,7 @@ Optional properties:
>    - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
>      The first cell is the IRQ number.
>      The second cell is the flags, encoded as the trigger masks from
> -    Documentation/devicetree/bindings/interrupts.txt
> +    Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>  
>    - clocks : A list of up to two phandle and clock specifier pairs
>    - clock-names : A list of clock names sorted in the same order as clocks.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org â Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/