linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Todd Poynor <toddpoynor@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] alarmtimer: add functions for timerfd support
Date: Wed, 15 May 2013 14:50:02 -0700	[thread overview]
Message-ID: <5194030A.7040106@linaro.org> (raw)
In-Reply-To: <1368653892-18939-2-git-send-email-toddpoynor@google.com>

On 05/15/2013 02:38 PM, Todd Poynor wrote:
> Add functions needed for hooking up alarmtimer to timerfd:
>
> * alarm_restart: Similar to hrtimer_restart, restart an alarmtimer after
>    the expires time has already been updated (as with alarm_forward).
>
> * alarm_forward_now: Similar to hrtimer_forward_now, move the expires
>    time forward to an interval from the current time of the associated clock.
>
> * alarm_start_relative: Start an alarmtimer with an expires time relative to
>    the current time of the associated clock.
>
> * alarm_expires_remaining: Similar to hrtimer_expires_remaining, return the
>    amount of time remaining until alarm expiry.
>
> Signed-off-by: Todd Poynor <toddpoynor@google.com>

Acked-by: John Stultz <john.stultz@linaro.org>

I'll queue this in my tree for 3.11, but I need to sort out which path 
the timerfd code needs to go upstream.

thanks
-john

  reply	other threads:[~2013-05-15 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 21:38 [PATCH 0/2] timerfd support for wakeup alarm timers Todd Poynor
2013-05-15 21:38 ` [PATCH 1/2] alarmtimer: add functions for timerfd support Todd Poynor
2013-05-15 21:50   ` John Stultz [this message]
2013-05-15 21:38 ` [PATCH 2/2] timerfd: add alarm timers Todd Poynor
2013-05-15 21:51   ` John Stultz
2013-05-23  1:20     ` John Stultz

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=5194030A.7040106@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=toddpoynor@google.com \
    /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).