linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched_clock: Remove deprecated setup_sched_clock() API
Date: Tue, 22 Apr 2014 13:41:11 -0700	[thread overview]
Message-ID: <5356D3E7.40009@linaro.org> (raw)
In-Reply-To: <1397003599-22386-1-git-send-email-sboyd@codeaurora.org>

On 04/08/2014 05:33 PM, Stephen Boyd wrote:
> Remove the 32-bit only setup_sched_clock() API now that all users
> have been converted to the 64-bit friendly sched_clock_register().
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

Got this queued for 3.16. Thanks!
-john


      parent reply	other threads:[~2014-04-22 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  0:33 [PATCH] sched_clock: Remove deprecated setup_sched_clock() API Stephen Boyd
2014-04-17 18:30 ` Stephen Boyd
2014-04-22 20:41 ` John Stultz [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=5356D3E7.40009@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).