From: John Stultz <john.stultz@linaro.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Will Deacon <will.deacon@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arm@kernel.org" <arm@kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv2 0/6] Make ARM's sched_clock generic + 64 bit friendly
Date: Mon, 17 Jun 2013 09:23:00 -0700 [thread overview]
Message-ID: <51BF37E4.8020006@linaro.org> (raw)
In-Reply-To: <20130616094501.GG10269@tarshish>
On 06/16/2013 02:45 AM, Baruch Siach wrote:
> Hi John,
>
> On Tue, Jun 04, 2013 at 10:53:04AM -0700, John Stultz wrote:
>> On 06/04/2013 09:09 AM, Will Deacon wrote:
>>> On Tue, Jun 04, 2013 at 01:19:48AM +0100, John Stultz wrote:
>>>> On 06/01/2013 11:39 PM, Stephen Boyd wrote:
>>>>> This is mostly a resend of a patch series I sent a little over a month
>>>>> ago. I've reordered the patches so that John can pick up the first three
>>>>> and get a generic sched_clock layer without having to take the 64 bit
>>>>> patches. The last three patches add 64 bit support and move the architected
>>>>> timers on ARM64 and ARM to use it.
>>>> Yea, so from the initial look over it, I think I'm happy with queuing
>>>> the first three patches, although I'd like to get some acks from arm
>>>> folks on at least the first two, just so no one is surprised with it
>>>> going through the -tip tree.
>>> The first two patches are pretty simple so, FWIW, you can add my ack on those:
>>>
>>> Acked-by: Will Deacon <will.deacon@arm.com>
>> Thanks! Added to the commits.
> What is the status of this series then? Is there a chance of seeing it in
> 3.11? I want to base some xtensa architecture work on this, so I'd like to
> know whether there is a stable base to start from.
I've got the first three in my internal tree, and was going to send it
by Thomas for 3.11 this week.
Thanks for the ping!
-john
next prev parent reply other threads:[~2013-06-17 16:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 6:39 [PATCHv2 0/6] Make ARM's sched_clock generic + 64 bit friendly Stephen Boyd
2013-06-02 6:39 ` [PATCHv2 1/6] ARM: sched_clock: Remove unused needs_suspend member Stephen Boyd
2013-06-02 6:39 ` [PATCHv2 2/6] ARM: sched_clock: Return suspended count earlier Stephen Boyd
2013-06-02 6:39 ` [PATCHv2 3/6] sched_clock: Make ARM's sched_clock generic for all architectures Stephen Boyd
2013-06-03 7:12 ` Baruch Siach
2013-06-03 19:50 ` Stephen Boyd
2013-06-04 17:56 ` John Stultz
2013-06-04 18:16 ` Russell King - ARM Linux
2013-06-21 15:45 ` Arnd Bergmann
2013-06-21 17:05 ` Stephen Boyd
2013-06-21 17:42 ` John Stultz
2013-06-24 22:45 ` Stephen Boyd
2013-06-24 22:54 ` John Stultz
2013-06-02 6:39 ` [PATCHv2 4/6] sched_clock: Add support for >32 bit sched_clock Stephen Boyd
2013-06-03 9:39 ` Russell King - ARM Linux
2013-06-03 21:11 ` Stephen Boyd
2013-06-03 22:12 ` Russell King - ARM Linux
2013-06-04 1:51 ` Stephen Boyd
2013-06-04 10:21 ` Russell King - ARM Linux
2013-06-10 4:12 ` Rob Herring
2013-06-14 17:17 ` Catalin Marinas
2013-06-10 15:16 ` anish singh
2013-06-10 15:38 ` Russell King - ARM Linux
2013-06-10 16:01 ` anish singh
2013-06-10 16:08 ` Russell King - ARM Linux
2013-06-02 6:39 ` [PATCHv2 5/6] ARM: arch_timer: Move to setup_sched_clock_64() Stephen Boyd
2013-06-02 6:39 ` [PATCHv2 6/6] arm64: Move to generic sched_clock infrastructure Stephen Boyd
2013-06-03 8:52 ` [PATCHv2 0/6] Make ARM's sched_clock generic + 64 bit friendly Baruch Siach
2013-06-04 0:19 ` John Stultz
2013-06-04 16:09 ` Will Deacon
2013-06-04 17:53 ` John Stultz
2013-06-16 9:45 ` Baruch Siach
2013-06-17 16:23 ` John Stultz [this message]
2013-06-17 18:02 ` Baruch Siach
2013-06-17 18:14 ` John Stultz
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=51BF37E4.8020006@linaro.org \
--to=john.stultz@linaro.org \
--cc=Catalin.Marinas@arm.com \
--cc=arm@kernel.org \
--cc=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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).