From: Stephen Boyd <sboyd@codeaurora.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Chris Zankel <chris@zankel.net>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
LKML <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH] xtensa: Switch to sched_clock_register()
Date: Thu, 12 Dec 2013 15:54:32 -0800 [thread overview]
Message-ID: <52AA4CB8.1010008@codeaurora.org> (raw)
In-Reply-To: <528CFEE9.3060108@codeaurora.org>
On 11/20/13 10:26, Stephen Boyd wrote:
> On 11/17/13 12:27, Max Filippov wrote:
>> On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>>> The 32 bit sched_clock interface now supports 64 bits. Upgrade
>>> to the 64 bit function to allow us to remove the 32 bit
>>> registration interface.
>>>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>>
>>> Patch is based on Linus' tip. Not event compile tested.
>>>
>>> arch/xtensa/kernel/time.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> Build and run-tested, appears to work.
>> Acked-by: Max Filippov <jcmvbkbc@gmail.com>
>>
>> Should it go through xtensa tree, or through some other tree as a part
>> of a bigger conversion series?
> If it can go through xtensa that sounds like the best option. Otherwise
> we can send it through the tip/timers tree.
>
Ping? I don't see this patch in linux-next yet so should I send this
through the tip/timers tree?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-12-12 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 23:31 [PATCH] xtensa: Switch to sched_clock_register() Stephen Boyd
2013-11-17 20:27 ` Max Filippov
2013-11-20 18:26 ` Stephen Boyd
2013-12-12 23:54 ` Stephen Boyd [this message]
2013-12-13 0:00 ` czankel
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=52AA4CB8.1010008@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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.