From: Saravana Kannan <skannan@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
"Turquette, Mike" <mturquette@ti.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Grant Likely <grant.likely@secretlab.ca>,
h@pengutronix.de, Jamie Iles <jamie@jamieiles.com>,
Jeremy Kerr <jeremy.kerr@canonical.com>,
Magnus Damm <magnus.damm@gmail.com>,
Deepak Saxena <dsaxena@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergman <arnd.bergmann@linaro.org>,
linux-arm-msm@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Richard Zhao <richard.zhao@linaro.org>,
Shawn Guo <shawn.guo@freescale.com>,
Paul Walmsley <paul@pwsan.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH] clk: Use a separate struct for holding init data.
Date: Tue, 01 May 2012 11:03:57 -0700 [thread overview]
Message-ID: <4FA0258D.8020807@codeaurora.org> (raw)
In-Reply-To: <20120501170001.GB4089@opensource.wolfsonmicro.com>
On 05/01/2012 10:00 AM, Mark Brown wrote:
> On Tue, May 01, 2012 at 11:13:34AM +0200, Andrew Lunn wrote:
>
>> I agree with you as well, it is frustrating. Could we agree, that once
>> this patch is in, we freeze the core until the start of the next
>> cycle. We use the remainder of this cycle for porting platforms to the
>> generic clock framework.
>
> Or merge the platforms then do framework changes incrementally, updating
> the platforms as we go (which is the normal pattern for maintaining a
> framework...). I see we've already got SPEAr merged.
Sorry for the annoyance I seem to have caused. I too have been trying to
get this in for a while before the other platforms started using the new
framework. Not everyone was free at the same time and it's taken longer
that I would have wished for.
I did my best to limit the changes that would be needed without making
my patch useless. Appreciate your understanding.
Regards,
Saravana
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-05-01 18:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 5:58 [PATCH] clk: Use a separate struct for holding init data Saravana Kannan
2012-04-26 6:28 ` Saravana Kannan
2012-04-26 8:42 ` Sascha Hauer
2012-04-26 9:36 ` Saravana Kannan
2012-04-26 9:51 ` Sascha Hauer
2012-04-30 19:30 ` Saravana Kannan
2012-04-30 22:19 ` Turquette, Mike
2012-04-30 22:46 ` Saravana Kannan
2012-05-01 8:11 ` Shawn Guo
2012-05-01 9:13 ` Andrew Lunn
2012-05-01 17:00 ` Mark Brown
2012-05-01 18:03 ` Saravana Kannan [this message]
2012-05-01 18:19 ` Mark Brown
2012-05-02 1:56 ` Mike Turquette
2012-05-02 2:14 ` Shawn Guo
2012-05-02 5:16 ` Andrew Lunn
2012-05-02 19:19 ` Mike Turquette
2012-05-02 13:32 ` Arnd Bergmann
2012-05-02 15:28 ` Mark Brown
2012-05-01 18:04 ` Andrew Lunn
2012-04-26 8:39 ` Sascha Hauer
2012-04-26 9:15 ` Saravana Kannan
2012-04-26 9:49 ` Mark Brown
2012-05-02 2:04 ` Mike Turquette
2012-05-02 4:42 ` Saravana Kannan
2012-05-02 19:07 ` Mike Turquette
2012-05-02 9:58 ` Sascha Hauer
2012-05-02 10:02 ` Russell King - ARM Linux
2012-05-02 10:11 ` Sascha Hauer
2012-05-03 23:03 ` Domenico Andreoli
2012-05-04 1:11 ` Saravana Kannan
2012-05-04 6:50 ` Domenico Andreoli
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=4FA0258D.8020807@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=amit.kucheria@linaro.org \
--cc=andrew@lunn.ch \
--cc=arnd.bergmann@linaro.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dsaxena@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=h@pengutronix.de \
--cc=jamie@jamieiles.com \
--cc=jeremy.kerr@canonical.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mturquette@ti.com \
--cc=paul@pwsan.com \
--cc=richard.zhao@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@codeaurora.org \
--cc=shawn.guo@freescale.com \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
/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).