linux-kernel - Re: [PATCH] xtensa: Switch to sched_clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Dec 2013 15:54:32 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Max Filippov <jcmvbkbc@...il.com>
CC:	Chris Zankel <chris@...kel.net>,
	"linux-xtensa@...ux-xtensa.org" <linux-xtensa@...ux-xtensa.org>,
	LKML <linux-kernel@...r.kernel.org>,
	John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH] xtensa: Switch to sched_clock_register()

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@...eaurora.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@...eaurora.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@...il.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/