From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: at91: trivial: typo in peripheral clock description
Date: Wed, 17 Jun 2015 16:36:01 +0200 [thread overview]
Message-ID: <20150617163601.213e9e67@bbrezillon> (raw)
In-Reply-To: <1434547371-12123-1-git-send-email-nicolas.ferre@atmel.com>
On Wed, 17 Jun 2015 15:22:51 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> Documentation/devicetree/bindings/clock/at91-clock.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/at91-clock.txt b/Documentation/devicetree/bindings/clock/at91-clock.txt
> index 7a4d4926f44e..5ba6450693b9 100644
> --- a/Documentation/devicetree/bindings/clock/at91-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/at91-clock.txt
> @@ -248,7 +248,7 @@ Required properties for peripheral clocks:
> - #address-cells : shall be 1 (reg is used to encode clk id).
> - clocks : shall be the master clock phandle.
> e.g. clocks = <&mck>;
> -- name: device tree node describing a specific system clock.
> +- name: device tree node describing a specific peripheral clock.
> * #clock-cells : from common clock binding; shall be set to 0.
> * reg: peripheral id. See Atmel's datasheets to get a full
> list of peripheral ids.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-17 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:22 [PATCH] clk: at91: trivial: typo in peripheral clock description Nicolas Ferre
2015-06-17 14:36 ` Boris Brezillon [this message]
2015-06-17 14:45 ` Alexandre Belloni
2015-06-17 14:59 ` Nicolas Ferre
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=20150617163601.213e9e67@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).