From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: clkfw: Moved the .init callback in the clk_register
Date: Wed, 13 May 2009 14:20:15 +0000 [thread overview]
Message-ID: <4A0AD71F.9050406@st.com> (raw)
In-Reply-To: <1242050283-7986-1-git-send-email-francesco.virlinzi@st.com>
Rebased on the latest git as suggested by Magnus.
Jean-Christophe PLAGNIOL-VILLARD ha scritto:
> On 14:27 Wed 13 May , Francesco VIRLINZI wrote:
>
>> This patch moves the .init callback in the clk_register function.
>> Moreover not the .init callback return a value:
>> - zero means the initialization is ok and the clock can be registered.
>> - any value not zero means there is a problem in the initialization and
>> the clkfw rejects the clock registration
>>
>> Signed-off-by: Francesco Virlinzi <francesco.virlinzi@st.com>
>> ---
>>
> what the diff against the precedent version?
>
> it will be nice if you can put here the update between each version
>
> Best Regards,
> J.
>
>
next prev parent reply other threads:[~2009-05-13 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 13:58 [PATCH] sh: clkfw: Moved the .init callback in the clk_regsiter Francesco VIRLINZI
2009-05-12 21:42 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-13 6:08 ` [PATCH] sh: clkfw: Moved the .init callback in the clk_register function [v3] Francesco VIRLINZI
2009-05-13 7:32 ` [PATCH] sh: clkfw: Moved the .init callback in the clk_regsiter Francesco VIRLINZI
2009-05-13 10:51 ` [PATCH] sh: clkfw: Moved the .init callback in the clk_register Magnus Damm
2009-05-13 12:27 ` [PATCH] sh: clkfw: Moved the .init callback in the clk_register function [v4] Francesco VIRLINZI
2009-05-13 14:12 ` [PATCH] sh: clkfw: Moved the .init callback in the Jean-Christophe PLAGNIOL-VILLARD
2009-05-13 14:20 ` Francesco VIRLINZI [this message]
2009-05-14 3:52 ` [PATCH] sh: clkfw: Moved the .init callback in the clk_register function [v4] Paul Mundt
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=4A0AD71F.9050406@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.