From: Linus Walleij <linus.walleij@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Turquette, Mike" <mturquette@ti.com>,
Ulf Hansson <ulf.hansson@stericsson.com>,
linux-arm-kernel@lists.infradead.org,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Philippe Begnic <philippe.begnic@st.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>
Subject: Re: [PATCH 1/4] clk: Provide option for clk_get_rate to issue hw for new rate
Date: Fri, 7 Sep 2012 23:34:01 +0200 [thread overview]
Message-ID: <CACRpkdbZSk7tTjG_-6NLoczbAGSCs4eqygFY7UmAkz+oQYOjVA@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFrTTcNfQ2d24oSWEsvw1OF6t91nv6Y_JQfiWx8Un7_u-A@mail.gmail.com>
On Fri, Sep 7, 2012 at 2:29 PM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On 7 September 2012 10:21, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Fri, Sep 7, 2012 at 3:00 AM, Turquette, Mike <mturquette@ti.com> wrote:
>>> On Thu, Sep 6, 2012 at 5:19 PM, Mike Turquette <mturquette@ti.com> wrote:
>>>> I'll take this series into clk-next.
>>>
>>> Oops, I forgot to ask about patch #3. Which tree do you want that to
>>> go through?
>>
>> Just take it all through your tree if there are no major conflicts.
>> Acked-by etc.
>
> Agree, it makes it simpler to go through Mike's clock tree. At least
> let's try it out.
> I will likely have similar patch series with cross dependencies later
> on, so this can be a good first test and hopefully it works.
That will probably hit the next merge window anyway - these
patches will go into v3.7 as it looks, then you can finalize the
next series for v3.8.
> Although, don't we need an ack by Samuel Ortiz for the patch on mfd?
> "mfd: dbx500: Provide a more accurate smp_twd clock"
Confused, isn't that patch part of the latter series, and not
part of what Mike merged?
> Or, is it enough with Linus ack since he is the maintainer of that
> specific mfd file I have patched?
That's up to Mike, but I hardly think Sam is going to get very
angry about this if we merge it.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-09-07 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 12:21 [PATCH 0/4] clk: Support for smp_twd clock for ux500 Ulf Hansson
2012-08-31 12:21 ` [PATCH 1/4] clk: Provide option for clk_get_rate to issue hw for new rate Ulf Hansson
2012-08-31 19:29 ` Mike Turquette
2012-09-06 9:09 ` Ulf Hansson
[not found] ` <20120907001927.20289.41627@nucleus>
2012-09-07 1:00 ` Turquette, Mike
2012-09-07 8:21 ` Linus Walleij
2012-09-07 12:29 ` Ulf Hansson
2012-09-07 21:34 ` Linus Walleij [this message]
2012-08-31 12:21 ` [PATCH 2/4] clk: ux500: Support for prmcu_rate clock Ulf Hansson
2012-08-31 12:21 ` [PATCH 3/4] mfd: dbx500: Provide a more accurate smp_twd clock Ulf Hansson
2012-09-19 16:02 ` Samuel Ortiz
2012-09-19 16:42 ` Mike Turquette
2012-09-19 16:56 ` Samuel Ortiz
2012-08-31 12:21 ` [PATCH 4/4] clk: ux500: Define smp_twd clock for u8500 Ulf Hansson
2012-08-31 23:32 ` [PATCH 0/4] clk: Support for smp_twd clock for ux500 Linus Walleij
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=CACRpkdbZSk7tTjG_-6NLoczbAGSCs4eqygFY7UmAkz+oQYOjVA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=philippe.begnic@st.com \
--cc=sameo@linux.intel.com \
--cc=srinidhi.kasagar@stericsson.com \
--cc=ulf.hansson@linaro.org \
--cc=ulf.hansson@stericsson.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: 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;
as well as URLs for NNTP newsgroup(s).