From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: at91/dt: sam9263: Fix typo: ac91_clk -> ac97_clk
Date: Wed, 10 Dec 2014 11:04:33 +0100 [thread overview]
Message-ID: <54881AB1.3040609@atmel.com> (raw)
In-Reply-To: <2676241.BfXNcaGQ7Q@kongar>
Le 05/12/2014 16:00, Alexander Stein a ?crit :
> On Friday 05 December 2014, 15:16:55 wrote Alexander Stein:
>> That clock should be called ac97_clk.
>>
>> Signed-off-by: Alexander Stein <alexanders83@web.de>
>> ---
>> arch/arm/boot/dts/at91sam9263.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/at91sam9263.dtsi b/arch/arm/boot/dts/at91sam9263.dtsi
>> index 7989756..5ed2810 100644
>> --- a/arch/arm/boot/dts/at91sam9263.dtsi
>> +++ b/arch/arm/boot/dts/at91sam9263.dtsi
>> @@ -294,7 +294,7 @@
>> reg = <17>;
>> };
>>
>> - ac91_clk: ac97_clk {
>> + ac97_clk: ac97_clk {
>> #clock-cells = <0>;
>> reg = <18>;
>> };
>>
>
> Please ignore those 2 patches for now. I made a mistake during local rebase.
Well at least this one (1/2) is valid and applies on my new
at91-3.20-dt. So I take it for now: tell me if you feel otherwise.
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Bye,
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Nicolas Ferre
prev parent reply other threads:[~2014-12-10 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 14:16 [PATCH 1/2] ARM: at91/dt: sam9263: Fix typo: ac91_clk -> ac97_clk Alexander Stein
2014-12-05 14:16 ` [PATCH 2/2] ARM: at91/dt: sam9263: Add missing clocks to ac97 node Alexander Stein
2014-12-10 10:05 ` Nicolas Ferre
2014-12-05 15:00 ` [PATCH 1/2] ARM: at91/dt: sam9263: Fix typo: ac91_clk -> ac97_clk Alexander Stein
2014-12-10 10:04 ` 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=54881AB1.3040609@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).