From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/13] SPEAr: Move to common clock framework
Date: Wed, 18 Apr 2012 23:13:03 +0200 [thread overview]
Message-ID: <20120418211303.GE3852@pengutronix.de> (raw)
In-Reply-To: <CAJOA=zNnZXdEwdswj31WHDoWjvRGz0fYUb99R0U=Qq9kX0EZHQ@mail.gmail.com>
On Wed, Apr 18, 2012 at 01:45:42PM -0700, Turquette, Mike wrote:
> On Tue, Apr 17, 2012 at 7:34 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 17 April 2012, Viresh Kumar wrote:
> >> SPEAr now supports common clock framework. This patchset contains changes
> >> related to this. It also contain few dependency commits for clock framework that
> >> are earlier sent separately.
> >>
> >> @Mike: It would be easiest to get these through ARM-SoC tree. So, would need
> >> your Acked-by on these patches. But firstly they must get reivewed :)
> >
> > We should agree on how we want to do the common clk patches for v3.5.
> > The two options I see are either we take all the patches that Mike
> > Acks into arm-soc, or Mike applies the patches in his own tree and
> > submits them to arm-soc. I think either way is fine for me, but
> > some people might feel strongly one way or another.
>
> I would prefer the latter (I maintain a branch and submit it). Is
> arm-soc still the right place for common clk patches in 3.5 and
> beyond? I don't mind hosting a branch for inclusion into linux-next
> and sending a pull request to Linus. There is nothing ARM-specific
> about the common framework.
Either way is fine with me, but it's really important that all the
floating clock framework patches begin to materialize in a visible
branch.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-04-18 21:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 11:15 [PATCH 00/13] SPEAr: Move to common clock framework Viresh Kumar
2012-04-17 11:15 ` [PATCH 01/13] CLKDEV: Add helper routines to allocate and add clkdevs for given struct clk * Viresh Kumar
2012-04-17 11:15 ` [PATCH 02/13] clk: Fix typo in comment Viresh Kumar
2012-04-18 21:04 ` Turquette, Mike
2012-04-17 11:15 ` [PATCH 03/13] " Viresh Kumar
2012-04-17 11:15 ` [PATCH 04/13] clk: clk-private: Add DEFINE_CLK macro Viresh Kumar
2012-04-18 21:01 ` Turquette, Mike
2012-04-17 11:15 ` [PATCH 05/13] clk: clk-gate: Create clk_gate_endisable() Viresh Kumar
2012-04-18 21:02 ` Turquette, Mike
2012-04-17 11:15 ` [PATCH 06/13] clk: Don't set clk->new_rate twice Viresh Kumar
2012-04-18 21:08 ` Turquette, Mike
2012-04-17 11:15 ` [PATCH 07/13] clk: clk_set_rate() must fail if CLK_SET_RATE_GATE is set and clk is enabled Viresh Kumar
2012-04-17 11:15 ` [PATCH 08/13] SPEAr: clk: Add VCO-PLL Synthesizer clock Viresh Kumar
2012-04-17 11:15 ` [PATCH 09/13] SPEAr: clk: Add Auxiliary " Viresh Kumar
2012-04-17 18:51 ` Sascha Hauer
2012-04-17 20:30 ` Arnd Bergmann
2012-04-18 20:01 ` Sascha Hauer
2012-04-17 11:15 ` [PATCH 10/13] SPEAr: clk: Add Fractional " Viresh Kumar
2012-04-17 11:15 ` [PATCH 11/13] SPEAr: clk: Add General Purpose Timer " Viresh Kumar
2012-04-17 11:15 ` [PATCH 13/13] SPEAr: Call clk_prepare() before calling clk_enable Viresh Kumar
2012-04-17 17:46 ` Sergei Shtylyov
2012-04-18 21:17 ` Turquette, Mike
[not found] ` <CAOh2x=maawrRjHhE3oGXfMOvsUbCkp9gWA_Kq-S0Dh7r6co6VA@mail.gmail.com>
2012-04-19 18:56 ` Turquette, Mike
2012-04-17 14:34 ` [PATCH 00/13] SPEAr: Move to common clock framework Arnd Bergmann
2012-04-17 14:57 ` Shawn Guo
2012-04-18 20:49 ` Turquette, Mike
2012-04-18 20:45 ` Turquette, Mike
2012-04-18 21:13 ` Sascha Hauer [this message]
2012-04-18 21:22 ` Turquette, Mike
2012-04-18 21:25 ` Turquette, Mike
[not found] ` <CAOh2x=nhZLQejWJb1Wdv=G9vU0hq+8CO0SSx95qQUJogL5ftNQ@mail.gmail.com>
2012-04-19 0:17 ` Turquette, Mike
2012-04-19 8:57 ` Arnd Bergmann
2012-04-19 9:16 ` Viresh Kumar
2012-04-19 10:53 ` Arnd Bergmann
2012-04-19 19:01 ` Turquette, Mike
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=20120418211303.GE3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).