From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/8]: omap4: clk: move clock data under drivers/clk
Date: Fri, 22 Mar 2013 11:32:34 +0200 [thread overview]
Message-ID: <1363944754.15426.186.camel@sokoban> (raw)
In-Reply-To: <514BEC05.3050105@ti.com>
On Fri, 2013-03-22 at 10:58 +0530, Rajendra Nayak wrote:
> Tero,
>
> On Thursday 21 March 2013 11:05 PM, Tero Kristo wrote:
> > Hi,
> >
> > This is an RFC version of the clock data move under drivers/clk.
> > Tested under 3.8 and boots fine, but don't try this out unless
> > you are experimental sort (I quickly tried with 3.9-rc3 and it failed to
> > boot with that.)
> >
> > The approach taken here has minimal impact on the clock data
> > and should make it easy to transfer clock data for omap2 / omap3 and
> > omap5 also. omap4 was only done as a proof of concept.
> >
> > Any comments appreciated.
>
> I strangely only see the cover letter delivered to me and no
> patches. Do you have a branch with the patches which you can
> share?
Keerthy had a similar question. It looks like TI people have had
problems with mailing list subscriptions as of late, and I am actually
also getting moderator bounces for my emails from linux-arm-kernel list
atm.
Anyway, I just pushed a branch here:
git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
branch: linux-3.8-omap4-clk-move
-Tero
prev parent reply other threads:[~2013-03-22 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 17:35 [RFC 0/8]: omap4: clk: move clock data under drivers/clk Tero Kristo
[not found] ` <1363887347-4686-2-git-send-email-t-kristo@ti.com>
2013-03-21 18:50 ` [RFC 1/8] RFC: CLK: OMAP: Add basic infrastructure for OMAP clocks Mike Turquette
2013-03-22 8:39 ` Tero Kristo
2013-03-22 16:47 ` Mike Turquette
2013-03-22 18:39 ` Tero Kristo
2013-03-22 20:01 ` Mike Turquette
2013-03-22 5:28 ` [RFC 0/8]: omap4: clk: move clock data under drivers/clk Rajendra Nayak
2013-03-22 9:32 ` Tero Kristo [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=1363944754.15426.186.camel@sokoban \
--to=t-kristo@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox