linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: at91: trivial: typo in peripheral clock description
Date: Wed, 17 Jun 2015 16:59:29 +0200	[thread overview]
Message-ID: <55818B51.4090506@atmel.com> (raw)
In-Reply-To: <20150617144517.GJ6549@piout.net>

Le 17/06/2015 16:45, Alexandre Belloni a ?crit :
> It is mandatory to always include a commit message :)

Something like:
s/system/peripheral/g
I suppose?

> On 17/06/2015 at 15:22:51 +0200, Nicolas Ferre wrote :
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.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.
>> -- 
>> 2.1.3
>>
> 


-- 
Nicolas Ferre

      reply	other threads:[~2015-06-17 14:59 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
2015-06-17 14:45 ` Alexandre Belloni
2015-06-17 14:59   ` Nicolas Ferre [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=55818B51.4090506@atmel.com \
    --to=nicolas.ferre@atmel.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).