From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 6/6] SPEAr: Switch to common clock framework
Date: Tue, 24 Apr 2012 09:39:37 +0530 [thread overview]
Message-ID: <4F962781.5020900@st.com> (raw)
In-Reply-To: <CAJOA=zOvyJ9pqEqnhmU1CqHy1uPUOyC=c7VtKjkjK91cbHkGHw@mail.gmail.com>
On 4/24/2012 2:12 AM, Turquette, Mike wrote:
> I also think that this code will not be affected by the changes to
> struct clk_hw which are expected from Saravana. Hopefully you have
> avoided a big rebase.
>
> I'll take these into my clk-next branch unless Arnd has any objection
> based on arm-soc collisions.
That sounds good.
I will send V3, for it. That will contain two additional dependency patches:
- clk: add a fixed factor clock - by Sascha Hauer
- CLKDEV: Add helper routines to allocate and add clkdevs for given struct clk *
--
viresh
prev parent reply other threads:[~2012-04-24 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 16:28 [PATCH V2 0/6] SPEAr: Move to common clock framework Viresh Kumar
2012-04-19 16:28 ` [PATCH V2 1/6] SPEAr: clk: Add VCO-PLL Synthesizer clock Viresh Kumar
2012-04-23 19:15 ` Turquette, Mike
2012-04-23 19:31 ` Turquette, Mike
2012-04-24 3:40 ` Viresh Kumar
2012-04-19 16:28 ` [PATCH V2 2/6] SPEAr: clk: Add Auxiliary " Viresh Kumar
2012-04-23 12:33 ` viresh kumar
2012-04-19 16:28 ` [PATCH V2 3/6] SPEAr: clk: Add Fractional " Viresh Kumar
2012-04-19 16:28 ` [PATCH V2 4/6] SPEAr: clk: Add General Purpose Timer " Viresh Kumar
2012-04-19 16:28 ` [PATCH V2 5/6] SPEAr: Call clk_prepare() before calling clk_enable Viresh Kumar
[not found] ` <ddade82f0666c3186b8a694aa2b79acd3f7e5d50.1334852395.git.viresh.kumar@st.com>
2012-04-19 19:59 ` [PATCH V2 6/6] SPEAr: Switch to common clock framework Arnd Bergmann
2012-04-20 3:28 ` Viresh Kumar
2012-04-20 16:02 ` Arnd Bergmann
2012-04-20 16:57 ` viresh kumar
2012-04-23 20:56 ` Turquette, Mike
[not found] ` <CAJOA=zOvyJ9pqEqnhmU1CqHy1uPUOyC=c7VtKjkjK91cbHkGHw@mail.gmail.com>
2012-04-24 4:09 ` Viresh Kumar [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=4F962781.5020900@st.com \
--to=viresh.kumar@st.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 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.