From: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
Cc: Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matthew Helsley
<matt.helsley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2)
Date: Fri, 8 Mar 2013 10:56:39 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1303081056040.22263@ionos> (raw)
In-Reply-To: <5139A409.3040805-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
On Fri, 8 Mar 2013, Pavel Emelyanov wrote:
> On 02/21/2013 10:21 PM, Pavel Emelyanov wrote:
> > Hi.
> >
> > Here's another approach to address the problems with insufficient API
> > of posix timers.
>
> Gentlemen,
Sir,
that caught my attention. Will move it up on my todo list :)
prev parent reply other threads:[~2013-03-08 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 18:21 [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2) Pavel Emelyanov
2013-02-21 18:22 ` [PATCH 2/3] posix-timers: Introduce /proc/<pid>/timers file Pavel Emelyanov
2013-02-21 18:22 ` [PATCH 3/3] posix-timers: Show sigevent info in proc file Pavel Emelyanov
[not found] ` <512665BA.9040802-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-02-21 18:22 ` [PATCH 1/3] posix timers: Allocate timer id per process (v2) Pavel Emelyanov
[not found] ` <512665E1.4040800-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-03-08 12:50 ` Thomas Gleixner
2013-03-08 8:40 ` [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2) Pavel Emelyanov
[not found] ` <5139A409.3040805-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-03-08 9:56 ` Thomas Gleixner [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=alpine.LFD.2.02.1303081056040.22263@ionos \
--to=tglx-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.helsley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.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 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).