From: Frederic Weisbecker <fweisbec@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@redhat.com>,
Chen Gang <gang.chen@asianux.com>
Subject: [PATCH 0/3] posix_timers: A few expiry caching fixes
Date: Sat, 30 Mar 2013 14:15:28 +0100 [thread overview]
Message-ID: <1364649331-30940-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
This series is on top of latest -mmotm.
[1/3] fixes some omitting sample capture after a build warning suddenly became visible
[2/3] fixes a wrong timer_gettime() result on a timer whose target has been reaped.
[3/3] needs some more thinking probably
Thanks.
Frederic Weisbecker (3):
posix-timers: Correctly get dying task time sample in
posix_cpu_timer_schedule()
posix_timers: Fix racy timer delta caching on task exit
posix_timers: Remove dead task timer expiry caching
kernel/posix-cpu-timers.c | 68 ++-------------------------------------------
1 files changed, 3 insertions(+), 65 deletions(-)
--
1.7.5.4
next reply other threads:[~2013-03-30 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 13:15 Frederic Weisbecker [this message]
2013-03-30 13:15 ` [PATCH 1/3] posix-timers: Correctly get dying task time sample in posix_cpu_timer_schedule() Frederic Weisbecker
2013-04-01 0:07 ` Chen Gang
2013-04-11 15:26 ` Frederic Weisbecker
2013-04-11 15:33 ` Chen Gang
2013-03-30 13:15 ` [PATCH 2/3] posix_timers: Fix racy timer delta caching on task exit Frederic Weisbecker
2013-03-30 13:15 ` [PATCH 3/3] posix_timers: Remove dead task timer expiry caching Frederic Weisbecker
2013-04-08 23:55 ` [PATCH 0/3] posix_timers: A few expiry caching fixes Andrew Morton
2013-04-11 15:19 ` Frederic Weisbecker
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=1364649331-30940-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gang.chen@asianux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=sgruszka@redhat.com \
--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
Powered by JetHome