linux-kernel - Re: [PATCH] msm: timer: Support sched

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:	Fri, 24 Feb 2012 09:32:26 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Marc Zyngier <marc.zyngier@....com>
CC:	David Brown <davidb@...eaurora.org>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] msm: timer: Support sched_clock()

Hi Marc,

On 02/24/12 09:24, Marc Zyngier wrote:
> On 24/02/12 17:09, David Brown wrote:
>> I'll keep an eye on it then, and push it into the ARM soc tree when
>> the dependencies are there.
> The whole thing is that there's no dependency. The sched_clock() stuff
> has hit mainline during the merge window. This patch could go in right
> now, without any harm.
>
> What Russell pulled is just a cleanup to convert the last two platforms
> having their own sched_clock() and not relying on our framework.
>
>

This patch relies on the fact that the HAVE_SCHED_CLOCK config option no
longer exists. We could push it in if the patch had that option added to
the Kconfig, but then it would conflict with the removal of the Kconfig
by 6905a65 (ARM: Make the sched_clock framework mandatory, 2012-01-18).

So I guess we send it through the arm-soc tree?

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
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/