From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mturquette@baylibre.com, sboyd@kernel.org, dt@kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devicetree: bindings: clock: Minor typo fix in the file armada3700-tbg-clock.txt
Date: Wed, 17 Mar 2021 10:29:39 -0700 [thread overview]
Message-ID: <1003e9ad-eb2b-70d6-76f1-c72ee59ebccd@infradead.org> (raw)
In-Reply-To: <20210317100840.2449462-1-unixbhaskar@gmail.com>
On 3/17/21 3:08 AM, Bhaskar Chowdhury wrote:
>
> s/provde/provide/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> .../devicetree/bindings/clock/armada3700-tbg-clock.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/armada3700-tbg-clock.txt b/Documentation/devicetree/bindings/clock/armada3700-tbg-clock.txt
> index 0ba1d83ff363..ed1df32c577a 100644
> --- a/Documentation/devicetree/bindings/clock/armada3700-tbg-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/armada3700-tbg-clock.txt
> @@ -1,6 +1,6 @@
> * Time Base Generator Clock bindings for Marvell Armada 37xx SoCs
>
> -Marvell Armada 37xx SoCs provde Time Base Generator clocks which are
> +Marvell Armada 37xx SoCs provide Time Base Generator clocks which are
> used as parent clocks for the peripheral clocks.
>
> The TBG clock consumer should specify the desired clock by having the
> --
--
~Randy
next prev parent reply other threads:[~2021-03-17 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 10:08 [PATCH] devicetree: bindings: clock: Minor typo fix in the file armada3700-tbg-clock.txt Bhaskar Chowdhury
2021-03-17 17:29 ` Randy Dunlap [this message]
2021-03-17 17:32 ` Randy Dunlap
2021-03-17 19:46 ` Bhaskar Chowdhury
2021-03-17 20:12 ` Randy Dunlap
2021-03-26 0:20 ` Rob Herring
2021-03-26 0:21 ` Rob Herring
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=1003e9ad-eb2b-70d6-76f1-c72ee59ebccd@infradead.org \
--to=rdunlap@infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=unixbhaskar@gmail.com \
/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).