From: pgaikwad@nvidia•com (Prashant Gaikwad)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/7] clk: tegra: Use common of_clk_init() function
Date: Fri, 1 Feb 2013 10:19:47 +0530 [thread overview]
Message-ID: <510B496B.2030303@nvidia.com> (raw)
In-Reply-To: <51020D94.4010509@wwwdotorg.org>
On Friday 25 January 2013 10:14 AM, Stephen Warren wrote:
> On 01/24/2013 04:57 PM, Mike Turquette wrote:
>> Quoting Stephen Warren (2013-01-24 11:32:37)
>>> On 01/24/2013 11:20 AM, Mike Turquette wrote:
>>>> Quoting Prashant Gaikwad (2013-01-04 18:44:48)
>>>>> On Friday 04 January 2013 10:00 PM, Stephen Warren wrote:
>>>>>> On 01/04/2013 12:00 AM, Prashant Gaikwad wrote:
>>>>>>> Use common of_clk_init() function for clocks initialization.
>>>>>>> drivers/clk/tegra/clk-tegra20.c | 3 ++-
>>>>>>> drivers/clk/tegra/clk-tegra30.c | 3 ++-
>>>>>> Oh, so this series is written assuming that the Tegra CCF rework is
>>>>>> already applied then? That makes the dependencies quite painful, since I
>>>>>> think we'll end up with the following order being needed:
>>>>>>
>>>>>> 1) clk: Add composite clock type
>>>>>> -> This would usually go through the clk tree.
>>>>>> 2) The Tegra CCF rework series
>>>>>> -> This must go through the Tegra tree due to lots of dependencies
>>>>>> and merge conflicts with other Tegra patches.
>>>>>> 3) This series
>>>>>> -> This would usually go through the clk tree.
>>>>>>
>>>>>> Is it possible to re-order the dependencies as (1) (3) (2), so that Mike
>>>>>> can apply (1) and (3) to the clock tree, then I can use the clk tree as
>>>>>> the basis for a branch in the Tegra tree to apply (2) and all the other
>>>>>> Tegra patches that will conflict with (2)?
>>>>> If Mike approves the concept and implementation in (1) and (3) then I
>>>>> will repost (2) and (3) with dependencies re-ordered.
>>>> Patch (1) still has some unaddressed comments, and is not a real
>>>> dependency for this series.
>>> I assume "Patch (1)" refers to the list of series a couple emails above,
>>> not the first patch in the series you're replying to; that threw me for
>>> a moment.
>>>
>>>> Since all of the patches have received their
>>>> Tested-by's then I propose to merge all patches from this series into
>>>> clk-next, which exception of patch 2/7 (the Tegra patch).
>>>>
>>>> This reduces your Tegra CCF conversion dependencies and you can role the
>>>> necessary of_clk_init change into your Tegra CCF conversion branch (it
>>>> has my implicit Ack and can be taken through your tree).
>>>>
>>>> Let me know if this is OK for you.
>>> OK, I'm happy to merge your clock tree into the Tegra tree and then
>>> apply 2/7 on top of the Tegra CCF work.
>> Hmm, maybe the clk tree needs to be a dependency branch of arm-soc
>> again, as it has in the past. Would that help with any Tegra merge
>> pain?
> Yes, I think that's what would end up happening if I merge the clk tree
> into the Tegra tree anyway.
Hi Mike,
Have you merged these patches for 3.9?
next prev parent reply other threads:[~2013-02-01 4:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 7:00 [PATCH 1/7] clk: add common of_clk_init() function Prashant Gaikwad
2013-01-04 7:00 ` [PATCH 2/7] clk: tegra: Use " Prashant Gaikwad
2013-01-04 16:30 ` Stephen Warren
2013-01-05 2:44 ` Prashant Gaikwad
2013-01-24 19:20 ` Mike Turquette
2013-01-24 19:32 ` Stephen Warren
[not found] ` <20130125005729.10623.61165@quantum>
2013-01-25 4:44 ` Stephen Warren
2013-02-01 4:49 ` Prashant Gaikwad [this message]
2013-02-01 22:53 ` Mike Turquette
2013-01-04 7:00 ` [PATCH 3/7] clk: sunxi: " Prashant Gaikwad
2013-01-04 7:00 ` [PATCH 4/7] clk: highbank: " Prashant Gaikwad
2013-01-18 17:55 ` Mike Turquette
2013-01-04 7:00 ` [PATCH 5/7] clk: vt8500: " Prashant Gaikwad
2013-01-18 17:56 ` Mike Turquette
2013-01-18 21:08 ` Tony Prisk
2013-01-24 19:15 ` Mike Turquette
2013-01-25 4:01 ` Tony Prisk
2013-01-04 7:00 ` [PATCH 6/7] clk: zynq: " Prashant Gaikwad
2013-01-04 7:00 ` [PATCH 7/7] clk: vexpress: " Prashant Gaikwad
2013-01-18 17:58 ` Mike Turquette
2013-01-21 16:03 ` Pawel Moll
2013-01-22 9:13 ` Linus Walleij
2013-01-23 10:54 ` Pawel Moll
2013-01-10 19:53 ` [PATCH 1/7] clk: add " Josh Cartwright
2013-01-11 5:01 ` Prashant Gaikwad
2013-01-13 8:57 ` Maxime Ripard
2013-01-24 17:47 ` Rob Herring
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=510B496B.2030303@nvidia.com \
--to=pgaikwad@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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