linux-kernel - Re: [PATCH 00/17] Convert ARM sched_clock users 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] [day] [month] [year] [list]

Message-ID: <87a9gx8g6i.fsf@linaro.org>
Date:	Thu, 21 Nov 2013 15:53:57 -0800
From:	Kevin Hilman <khilman@...aro.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Olof Johansson <olof@...om.net>,
	John Stultz <john.stultz@...aro.org>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 00/17] Convert ARM sched_clock users to sched_clock_register()

Stephen Boyd <sboyd@...eaurora.org> writes:

> On 11/21/13 15:10, Kevin Hilman wrote:
>> Hi Stephen,
>>
>> Stephen Boyd <sboyd@...eaurora.org> writes:
>>
>>> Olof,
>>>
>>> Please consider picking up these simple conversion patches. They
>>> were sent a few months back[1] but I didn't keep pushing them due
>>> to the complex path to mainline that the core patches took. I've
>>> picked up the acks and resent. Now that the core kernel changes have
>>> landed in Linus' tree it's much easier to pull these changes in.
>> Just to clarify, are the dependencies in v3.12? or were they merged for
>> the v3.13 merge window and just recently it Linus' tree.
>
> The dependencies are not in 3.12. They just hit Linus' tree this merge
> window (3.13). Ingo brought it into tip at commit
> 68e90740284c69292881cd38c7ece6f09a18a58f and Linus took it at commit
> 87093826aa0172d9135ca1f301c4298a258ceee6.

OK, thanks for the clarification.

I've applied these to an soc/sched_clock branch which is based on
tip/timers-core-for-linus and merged it into our to-build branch so it
gets some early boot/build coverage.  Once -rc1 is out, we'll start
adding non-fixes to for-next and this will be among the first branches
there (assuming the build/boot doesn't show any problems.)

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