All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] clk: tegra: Use common of_clk_init() function
Date: Fri, 04 Jan 2013 09:30:32 -0700	[thread overview]
Message-ID: <50E703A8.1080808@wwwdotorg.org> (raw)
In-Reply-To: <1357282858-2112-2-git-send-email-pgaikwad@nvidia.com>

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)?

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: mturquette@linaro.org, swarren@nvidia.com,
	grant.likely@secretlab.ca, linus.walleij@linaro.org,
	rob.herring@calxeda.com, maxime.ripard@free-electrons.com,
	linux@prisktech.co.nz, josh.cartwright@ni.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/7] clk: tegra: Use common of_clk_init() function
Date: Fri, 04 Jan 2013 09:30:32 -0700	[thread overview]
Message-ID: <50E703A8.1080808@wwwdotorg.org> (raw)
In-Reply-To: <1357282858-2112-2-git-send-email-pgaikwad@nvidia.com>

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)?

  reply	other threads:[~2013-01-04 16:30 UTC|newest]

Thread overview: 53+ 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 ` Prashant Gaikwad
2013-01-04  7:00 ` [PATCH 2/7] clk: tegra: Use " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-04 16:30   ` Stephen Warren [this message]
2013-01-04 16:30     ` Stephen Warren
2013-01-05  2:44     ` Prashant Gaikwad
2013-01-05  2:44       ` Prashant Gaikwad
2013-01-24 19:20       ` Mike Turquette
2013-01-24 19:20         ` Mike Turquette
2013-01-24 19:32         ` Stephen Warren
2013-01-24 19:32           ` Stephen Warren
     [not found]           ` <20130125005729.10623.61165@quantum>
2013-01-25  4:44             ` Stephen Warren
2013-01-25  4:44               ` Stephen Warren
2013-02-01  4:49               ` Prashant Gaikwad
2013-02-01  4:49                 ` Prashant Gaikwad
2013-02-01 22:53                 ` Mike Turquette
2013-02-01 22:53                   ` Mike Turquette
2013-01-04  7:00 ` [PATCH 3/7] clk: sunxi: " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-04  7:00 ` [PATCH 4/7] clk: highbank: " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-18 17:55   ` Mike Turquette
2013-01-18 17:55     ` Mike Turquette
2013-01-04  7:00 ` [PATCH 5/7] clk: vt8500: " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-18 17:56   ` Mike Turquette
2013-01-18 17:56     ` Mike Turquette
2013-01-18 21:08     ` Tony Prisk
2013-01-18 21:08       ` Tony Prisk
2013-01-24 19:15       ` Mike Turquette
2013-01-25  4:01         ` Tony Prisk
2013-01-25  4:01           ` Tony Prisk
2013-01-04  7:00 ` [PATCH 6/7] clk: zynq: " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-04  7:00 ` [PATCH 7/7] clk: vexpress: " Prashant Gaikwad
2013-01-04  7:00   ` Prashant Gaikwad
2013-01-18 17:58   ` Mike Turquette
2013-01-18 17:58     ` Mike Turquette
2013-01-21 16:03     ` Pawel Moll
2013-01-21 16:03       ` Pawel Moll
2013-01-22  9:13     ` Linus Walleij
2013-01-22  9:13       ` Linus Walleij
2013-01-23 10:54   ` Pawel Moll
2013-01-23 10:54     ` Pawel Moll
2013-01-10 19:53 ` [PATCH 1/7] clk: add " Josh Cartwright
2013-01-10 19:53   ` Josh Cartwright
2013-01-11  5:01   ` Prashant Gaikwad
2013-01-11  5:01     ` Prashant Gaikwad
2013-01-13  8:57 ` Maxime Ripard
2013-01-13  8:57   ` Maxime Ripard
2013-01-24 17:47 ` Rob Herring
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=50E703A8.1080808@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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.