From: Marc Zyngier <marc.zyngier@arm.com>
To: David Brown <davidb@codeaurora.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] msm: timer: Support sched_clock()
Date: Fri, 24 Feb 2012 10:11:14 +0000 [thread overview]
Message-ID: <4F476242.2020909@arm.com> (raw)
In-Reply-To: <20120222215533.GA31480@codeaurora.org>
On 22/02/12 21:55, David Brown wrote:
> On Tue, Feb 21, 2012 at 05:39:37PM -0800, Stephen Boyd wrote:
>> Now that sched_clock is mandatory on ARM it's simple to add
>> sched_clock support to the MSM timer code. Add it so that we get
>> more accurate sched_clock output than the jiffies based version
>> that's provided by default.
>>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>> Cc: David Brown <davidb@codeaurora.org>
>
> Marc, are you able to pull this into your series, so they can all go
> in together? If so:
>
> Acked-by: David Brown <davidb@codeaurora.org>
David, Stephen,
Russell already pulled my sched_clock() patch series, so I'm not sure it
is actually useful for me to carry it (and there is actually no
dependency between this patch and the series). Maybe putting it in the
patch system or via armsoc would be best?
Otherwise:
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2012-02-24 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 1:39 [PATCH] msm: timer: Support sched_clock() Stephen Boyd
2012-02-22 21:55 ` David Brown
2012-02-24 10:11 ` Marc Zyngier [this message]
2012-02-24 17:09 ` David Brown
2012-02-24 17:24 ` Marc Zyngier
2012-02-24 17:32 ` Stephen Boyd
2012-02-24 17:37 ` Marc Zyngier
2012-02-25 1:10 ` David Brown
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=4F476242.2020909@arm.com \
--to=marc.zyngier@arm.com \
--cc=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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 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).