From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 00/17] Convert ARM sched_clock users to sched_clock_register()
Date: Thu, 21 Nov 2013 15:53:57 -0800 [thread overview]
Message-ID: <87a9gx8g6i.fsf@linaro.org> (raw)
In-Reply-To: <528E955C.7090205@codeaurora.org> (Stephen Boyd's message of "Thu, 21 Nov 2013 15:21:00 -0800")
Stephen Boyd <sboyd@codeaurora•org> writes:
> On 11/21/13 15:10, Kevin Hilman wrote:
>> Hi Stephen,
>>
>> Stephen Boyd <sboyd@codeaurora•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
prev parent reply other threads:[~2013-11-21 23:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 23:26 [PATCH 00/17] Convert ARM sched_clock users to sched_clock_register() Stephen Boyd
2013-11-15 23:26 ` [PATCH 01/17] ARM: timer-sp: Switch " Stephen Boyd
2013-11-15 23:26 ` [PATCH 02/17] ARM: clps711x: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 03/17] ARM: davinci: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 04/17] ARM: imx: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 05/17] ARM: integrator: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 06/17] ARM: IXP4xx: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 07/17] ARM: mmp: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 08/17] ARM: msm: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 09/17] ARM: OMAP1: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 10/17] ARM: OMAP2+: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 11/17] ARM: pxa: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 12/17] ARM: sa1100: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 13/17] ARM: u300: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 14/17] ARM: iop: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 15/17] ARM: OMAP: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 16/17] ARM: orion: " Stephen Boyd
2013-11-15 23:26 ` [PATCH 17/17] ARM: versatile: " Stephen Boyd
2013-11-21 23:10 ` [PATCH 00/17] Convert ARM sched_clock users " Kevin Hilman
2013-11-21 23:21 ` Stephen Boyd
2013-11-21 23:53 ` Kevin Hilman [this message]
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=87a9gx8g6i.fsf@linaro.org \
--to=khilman@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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