From: Rajendra Nayak <rnayak@ti.com> To: Tero Kristo <t-kristo@ti.com> Cc: linux-omap@vger.kernel.org, tony@atomide.com, khilman@linaro.org, paul@pwsan.com, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 0/8]: omap4: clk: move clock data under drivers/clk Date: Fri, 22 Mar 2013 10:58:37 +0530 [thread overview] Message-ID: <514BEC05.3050105@ti.com> (raw) In-Reply-To: <1363887347-4686-1-git-send-email-t-kristo@ti.com> 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? regards, Rajendra > > -Tero > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak) To: linux-arm-kernel@lists.infradead.org Subject: [RFC 0/8]: omap4: clk: move clock data under drivers/clk Date: Fri, 22 Mar 2013 10:58:37 +0530 [thread overview] Message-ID: <514BEC05.3050105@ti.com> (raw) In-Reply-To: <1363887347-4686-1-git-send-email-t-kristo@ti.com> 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? regards, Rajendra > > -Tero > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >
next prev parent reply other threads:[~2013-03-22 5:28 UTC|newest] Thread overview: 23+ 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 2013-03-21 17:35 ` Tero Kristo 2013-03-21 17:35 ` [RFC 1/8] RFC: CLK: OMAP: Add basic infrastructure for OMAP clocks Tero Kristo 2013-03-21 18:50 ` Mike Turquette 2013-03-21 18:50 ` Mike Turquette 2013-03-22 8:39 ` Tero Kristo 2013-03-22 8:39 ` Tero Kristo 2013-03-22 16:47 ` Mike Turquette 2013-03-22 16:47 ` Mike Turquette 2013-03-22 18:39 ` Tero Kristo 2013-03-22 18:39 ` Tero Kristo 2013-03-22 20:01 ` Mike Turquette 2013-03-22 20:01 ` Mike Turquette 2013-03-21 17:35 ` [RFC 3/8] CLK: OMAP4: Clock header register declarations to struct Tero Kristo 2013-03-21 17:35 ` [RFC 4/8] CLK: OMAP4: copy over cclock44xx_data.c file from mach-omap2 Tero Kristo 2013-03-21 17:35 ` [RFC 5/8] CLK: OMAP4: modify clock data layout for the new driver format Tero Kristo 2013-03-21 17:35 ` [RFC 6/8] CLK: OMAP4: add support for the new clock init code Tero Kristo 2013-03-21 17:35 ` [RFC 7/8] clk: use strncmp for matching con_id in clk_find Tero Kristo 2013-03-21 17:35 ` [RFC 8/8] ARM: OMAP4: use new driver for omap4 clock data Tero Kristo 2013-03-22 5:28 ` Rajendra Nayak [this message] 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 2013-03-22 9:32 ` Tero Kristo
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=514BEC05.3050105@ti.com \ --to=rnayak@ti.com \ --cc=khilman@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.com \ --cc=t-kristo@ti.com \ --cc=tony@atomide.com \ /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: linkBe 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.