From: Guo Ren <guoren@kernel.org>
To: Flavio Suligoi <f.suligoi@asem.it>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <maz@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-csky@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] doc: devicetree: bindings: fix spelling mistake
Date: Sat, 13 Jun 2020 16:43:11 +0800 [thread overview]
Message-ID: <CAJF2gTTojGRnshstFwqu4xM_txeBOY=uFiWPTpXZPWv2uS6QqQ@mail.gmail.com> (raw)
In-Reply-To: <20200611095804.22026-1-f.suligoi@asem.it>
Acked-by: Guo Ren <guoren@kernel.org>
On Thu, Jun 11, 2020 at 5:58 PM Flavio Suligoi <f.suligoi@asem.it> wrote:
>
> Fix typo: "triger" --> "trigger"
>
> Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
> ---
> Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt | 2 +-
> .../devicetree/bindings/interrupt-controller/csky,mpintc.txt | 2 +-
> Documentation/devicetree/bindings/timer/csky,mptimer.txt | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt b/Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt
> index ba455589f869..e1c49b660d3a 100644
> --- a/Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt
> @@ -12,7 +12,7 @@ Required properties for the top level node:
> Only the GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW flags are supported.
> - #interrupt-cells : Specifies the number of cells needed to encode an
> interrupt. Should be 2. The first cell defines the interrupt number,
> - the second encodes the triger flags encoded as described in
> + the second encodes the trigger flags encoded as described in
> Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
> - compatible:
> - "mediatek,mt7621-gpio" for Mediatek controllers
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt b/Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt
> index e13405355166..e6bbcae4d07f 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt
> +++ b/Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt
> @@ -10,7 +10,7 @@ Interrupt number definition:
> 16-31 : private irq, and we use 16 as the co-processor timer.
> 31-1024: common irq for soc ip.
>
> -Interrupt triger mode: (Defined in dt-bindings/interrupt-controller/irq.h)
> +Interrupt trigger mode: (Defined in dt-bindings/interrupt-controller/irq.h)
> IRQ_TYPE_LEVEL_HIGH (default)
> IRQ_TYPE_LEVEL_LOW
> IRQ_TYPE_EDGE_RISING
> diff --git a/Documentation/devicetree/bindings/timer/csky,mptimer.txt b/Documentation/devicetree/bindings/timer/csky,mptimer.txt
> index 15cfec08fbb8..f5c7e99cf52b 100644
> --- a/Documentation/devicetree/bindings/timer/csky,mptimer.txt
> +++ b/Documentation/devicetree/bindings/timer/csky,mptimer.txt
> @@ -8,7 +8,7 @@ regs is accessed by cpu co-processor 4 registers with mtcr/mfcr.
> - PTIM_CTLR "cr<0, 14>" Control reg to start reset timer.
> - PTIM_TSR "cr<1, 14>" Interrupt cleanup status reg.
> - PTIM_CCVR "cr<3, 14>" Current counter value reg.
> - - PTIM_LVR "cr<6, 14>" Window value reg to triger next event.
> + - PTIM_LVR "cr<6, 14>" Window value reg to trigger next event.
>
> ==============================
> timer node bindings definition
> --
> 2.17.1
>
--
Best Regards
Guo Ren
ML: https://lore.kernel.org/linux-csky/
prev parent reply other threads:[~2020-06-13 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:58 [PATCH] doc: devicetree: bindings: fix spelling mistake Flavio Suligoi
2020-06-13 8:43 ` Guo Ren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJF2gTTojGRnshstFwqu4xM_txeBOY=uFiWPTpXZPWv2uS6QqQ@mail.gmail.com' \
--to=guoren@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=f.suligoi@asem.it \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).