From: Arnd Bergmann <arnd@arndb.de>
To: John Stultz <john.stultz@linaro.org>
Cc: linux-kernel@vger.kernel.org, "Arve Hjønnevåg" <arve@android.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Alessandro Zummo" <a.zummo@towertech.it>
Subject: Re: [PATCH 0/4] Posix Alarm Timers
Date: Wed, 20 Apr 2011 08:40:33 +0200 [thread overview]
Message-ID: <201104200840.33671.arnd@arndb.de> (raw)
In-Reply-To: <1303257510-15054-1-git-send-email-john.stultz@linaro.org>
On Wednesday 20 April 2011 01:58:26 John Stultz wrote:
>
> Just wanted to send out my current Posix Alarm Timers queue for
> comment and review in the hopes of getting it into shape for
> 2.6.40.
>
> Some background on the patches can be found here:
> https://lwn.net/Articles/429925/
>
> New in this series:
> * Added timekeeping_inject_sleeptime, which corrects CLOCK_BOOTTIME
> for arches that don't support read_persistent_clock().
> * I've added a CAP_WAKE_ALARM capability to limit random applications
> from setting alarms in the last patch. This probably needs some
> careful review as it allows clock_nanosleep and timer_create to
> return -EPERM, which is new behavior.
>
I haven't looked at these patches much before, so I've done a brief
review now. They look very nice, and I can't find anything to complain
about.
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2011-04-20 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 23:58 [PATCH 0/4] Posix Alarm Timers John Stultz
2011-04-19 23:58 ` [PATCH 1/4] time: Add timekeeping_inject_sleeptime John Stultz
2011-04-19 23:58 ` [PATCH 2/4] timers: Add rb_init_node() to allow for stack allocated rb nodes John Stultz
2011-04-19 23:58 ` [PATCH 3/4] timers: Introduce in-kernel alarm-timer interface John Stultz
2011-04-19 23:58 ` [PATCH 4/4] timers: posix interface for alarm-timers John Stultz
2011-04-20 6:34 ` Richard Cochran
2011-04-21 18:19 ` John Stultz
2011-04-20 6:40 ` Arnd Bergmann [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=201104200840.33671.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=a.zummo@towertech.it \
--cc=arve@android.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.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 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.