From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@arm.linux.org.uk>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Ralf Baechle <ralf@linux-mips.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] clk: Make the generic clock API available by default
Date: Thu, 30 Aug 2012 16:40:25 -0700 [thread overview]
Message-ID: <503FF9E9.4020701@wwwdotorg.org> (raw)
In-Reply-To: <20120830171918.GE4356@opensource.wolfsonmicro.com>
On 08/30/12 10:19, Mark Brown wrote:
> On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
>> On 08/28/12 13:35, Mark Brown wrote:
>
>>> @@ -674,6 +676,7 @@ config ARCH_TEGRA
>>> select GENERIC_CLOCKEVENTS
>>> select GENERIC_GPIO
>>> select HAVE_CLK
>>> + select HAVE_CUSTOM_CLK
>
>> For 3.7, Tegra will switch to the common clock framework. I think
>> this patch would then disable that. How should we resolve this -
>> rebase the Tegra common-clk tree on top of any branch containing
>> this patch in order to remove that select statement?
>
> I'd expect this to be applied on a separate branch so you should be able
> to rebase your conversion on top of it or merge it into your branch
> which should deal with things well enough I think?
That should work.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-mips@linux-mips.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Paul Mackerras <paulus@samba.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH] clk: Make the generic clock API available by default
Date: Thu, 30 Aug 2012 16:40:25 -0700 [thread overview]
Message-ID: <503FF9E9.4020701@wwwdotorg.org> (raw)
In-Reply-To: <20120830171918.GE4356@opensource.wolfsonmicro.com>
On 08/30/12 10:19, Mark Brown wrote:
> On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
>> On 08/28/12 13:35, Mark Brown wrote:
>
>>> @@ -674,6 +676,7 @@ config ARCH_TEGRA
>>> select GENERIC_CLOCKEVENTS
>>> select GENERIC_GPIO
>>> select HAVE_CLK
>>> + select HAVE_CUSTOM_CLK
>
>> For 3.7, Tegra will switch to the common clock framework. I think
>> this patch would then disable that. How should we resolve this -
>> rebase the Tegra common-clk tree on top of any branch containing
>> this patch in order to remove that select statement?
>
> I'd expect this to be applied on a separate branch so you should be able
> to rebase your conversion on top of it or merge it into your branch
> which should deal with things well enough I think?
That should work.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Make the generic clock API available by default
Date: Thu, 30 Aug 2012 16:40:25 -0700 [thread overview]
Message-ID: <503FF9E9.4020701@wwwdotorg.org> (raw)
In-Reply-To: <20120830171918.GE4356@opensource.wolfsonmicro.com>
On 08/30/12 10:19, Mark Brown wrote:
> On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
>> On 08/28/12 13:35, Mark Brown wrote:
>
>>> @@ -674,6 +676,7 @@ config ARCH_TEGRA
>>> select GENERIC_CLOCKEVENTS
>>> select GENERIC_GPIO
>>> select HAVE_CLK
>>> + select HAVE_CUSTOM_CLK
>
>> For 3.7, Tegra will switch to the common clock framework. I think
>> this patch would then disable that. How should we resolve this -
>> rebase the Tegra common-clk tree on top of any branch containing
>> this patch in order to remove that select statement?
>
> I'd expect this to be applied on a separate branch so you should be able
> to rebase your conversion on top of it or merge it into your branch
> which should deal with things well enough I think?
That should work.
next prev parent reply other threads:[~2012-08-30 23:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 20:35 [PATCH] clk: Make the generic clock API available by default Mark Brown
2012-08-28 20:35 ` Mark Brown
2012-08-28 20:35 ` Mark Brown
2012-08-29 5:56 ` Hans-Christian Egtvedt
2012-08-29 5:56 ` Hans-Christian Egtvedt
2012-08-29 5:56 ` Hans-Christian Egtvedt
2012-08-29 21:49 ` Stephen Warren
2012-08-29 21:49 ` Stephen Warren
2012-08-29 21:49 ` Stephen Warren
2012-08-30 17:19 ` Mark Brown
2012-08-30 17:19 ` Mark Brown
2012-08-30 17:19 ` Mark Brown
2012-08-30 23:40 ` Stephen Warren [this message]
2012-08-30 23:40 ` Stephen Warren
2012-08-30 23:40 ` Stephen Warren
2012-09-05 2:03 ` Benjamin Herrenschmidt
2012-09-05 2:03 ` Benjamin Herrenschmidt
2012-09-05 2:03 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 13:02 Mark Brown
2012-10-22 13:02 ` Mark Brown
2012-10-22 13:05 ` Russell King - ARM Linux
2012-10-22 13:05 ` Russell King - ARM Linux
2012-10-22 13:27 ` Mark Brown
2012-10-22 13:27 ` Mark Brown
2012-10-22 13:50 ` Russell King - ARM Linux
2012-10-22 13:50 ` Russell King - ARM Linux
2012-10-22 13:54 ` Mark Brown
2012-10-22 13:54 ` Mark Brown
2012-10-22 15:56 ` Stephen Warren
2012-10-22 15:56 ` Stephen Warren
2012-10-23 9:47 ` Mark Brown
2012-10-23 9:47 ` Mark Brown
2012-10-23 2:10 ` Kelvin Cheung
2012-10-23 9:22 ` Mark Brown
2012-10-23 9:22 ` Mark Brown
2012-10-23 9:54 Mark Brown
2012-10-23 9:54 ` Mark Brown
2012-11-26 21:39 ` Grant Likely
2012-11-26 21:39 ` Grant Likely
2012-11-26 21:39 ` Grant Likely
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=503FF9E9.4020701@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=egtvedt@samfundet.no \
--cc=gxt@mprc.pku.edu.cn \
--cc=hskinnemoen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.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.