All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] drivers/clocksource: sched_clock_register() conversion for 3.13 (via tip/timers/core)
Date: Mon, 30 Sep 2013 16:29:12 +0200	[thread overview]
Message-ID: <52498AB8.7090209@linaro.org> (raw)
In-Reply-To: <52448A46.9020207@linaro.org>

On 09/26/2013 09:25 PM, John Stultz wrote:
> Hey Daniel,
>      Here's the sched_clock_register conversion that Stephen did earlier
> this summer, as part of extending the generic sched_clock code to
> support 64bit counters. Unfortunately the prereqs for this series missed
> getting into tip/timers/core for 3.12, so I never sent out this pull
> request. But now that the prereqs are in tip/timers/core for 3.13, I've
> merge it up and I wanted to go ahead and send this out.
>
> This v2 pull request removes the setup_sched_clock deprecation, as that
> causes lots of warnings since there's still users in the arch/arm tree.
>
> Let me know if you have any issues or concerns.

Thanks John,

pulled in my tree as 3.13 material.

   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Linux ARM Kernel ML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL v2] drivers/clocksource: sched_clock_register() conversion for 3.13 (via tip/timers/core)
Date: Mon, 30 Sep 2013 16:29:12 +0200	[thread overview]
Message-ID: <52498AB8.7090209@linaro.org> (raw)
In-Reply-To: <52448A46.9020207@linaro.org>

On 09/26/2013 09:25 PM, John Stultz wrote:
> Hey Daniel,
>      Here's the sched_clock_register conversion that Stephen did earlier
> this summer, as part of extending the generic sched_clock code to
> support 64bit counters. Unfortunately the prereqs for this series missed
> getting into tip/timers/core for 3.12, so I never sent out this pull
> request. But now that the prereqs are in tip/timers/core for 3.13, I've
> merge it up and I wanted to go ahead and send this out.
>
> This v2 pull request removes the setup_sched_clock deprecation, as that
> causes lots of warnings since there's still users in the arch/arm tree.
>
> Let me know if you have any issues or concerns.

Thanks John,

pulled in my tree as 3.13 material.

   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2013-09-30 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 19:25 [GIT PULL v2] drivers/clocksource: sched_clock_register() conversion for 3.13 (via tip/timers/core) John Stultz
2013-09-26 19:25 ` John Stultz
2013-09-30 14:29 ` Daniel Lezcano [this message]
2013-09-30 14:29   ` Daniel Lezcano

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=52498AB8.7090209@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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.