From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: announcing the clk-next branch
Date: Wed, 25 Apr 2012 14:38:28 +0200 [thread overview]
Message-ID: <20120425123828.GC3852@pengutronix.de> (raw)
In-Reply-To: <CAJOA=zOGSh3et4nxE=JdojL4uDjgt8o+oiOU4pmbM=oU2U6prA@mail.gmail.com>
On Tue, Apr 24, 2012 at 06:32:20PM -0700, Turquette, Mike wrote:
> Hi all,
>
> The clock patches that I have signed-off on and picked from the list
> are all rebased on top of 3.4-rc4. They can be found here:
>
> git://git.linaro.org/people/mturquette/linux.git clk-next
Thanks Mike!
>
> If the branch is missing anything that I have ACK'd then please let me know.
You haven't acked it, but for i.MX I need two patches from Viresh I'd
like to base on:
[PATCH V3 1/8] CLKDEV: Add helper routines to allocate and add clkdevs for given struct clk *
[PATCH V3 2/8] clk: add a fixed factor clock
Also I need the patch implementing managed clk_get which currently sits
in Russells tree.
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-25 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 1:32 announcing the clk-next branch Turquette, Mike
2012-04-25 12:38 ` Sascha Hauer [this message]
2012-04-25 12:42 ` Russell King - ARM Linux
2012-04-25 15:15 ` Turquette, Mike
2012-04-26 3:56 ` Viresh Kumar
2012-04-30 14:41 ` Arnd Bergmann
2012-04-30 16:16 ` viresh kumar
2012-04-30 16:37 ` Arnd Bergmann
2012-04-30 16:40 ` viresh kumar
2012-04-30 17:00 ` Arnd Bergmann
2012-04-27 4:10 ` Viresh Kumar
2012-04-27 6:14 ` Viresh Kumar
2012-04-27 7:09 ` Shawn Guo
2012-04-27 17:54 ` Turquette, Mike
2012-04-28 4:52 ` Shawn Guo
2012-04-30 14:43 ` Arnd Bergmann
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=20120425123828.GC3852@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 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.