From: Pavel Tikhomirov <snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@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>,
Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
Pavel Tikhomirov
<snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/1] posix timers: Expand exitsting info in proc file
Date: Fri, 17 May 2013 02:12:02 +0400 [thread overview]
Message-ID: <1368742323-46949-1-git-send-email-snorcht@gmail.com> (raw)
Hi.
I'm working on the checkpoint-restore project (http://criu.org), on
realisation of posix-timers. To compleatly checkpoint and restore these
timers we need to know which clock they are using. So I d'like to add
this information to existing syscall which shows posix-timers info.
Pavel Tikhomirov (1):
posix-timers: Show clock ID in proc file
fs/proc/base.c | 1 +
1 file changed, 1 insertion(+)
--
1.7.9.5
next reply other threads:[~2013-05-16 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 22:12 Pavel Tikhomirov [this message]
[not found] ` <1368742323-46949-1-git-send-email-snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-16 22:12 ` [PATCH 1/1] posix-timers: Show clock ID in proc file Pavel Tikhomirov
[not found] ` <1368742323-46949-2-git-send-email-snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-17 15:59 ` Greg KH
2013-05-17 16:12 ` Pavel Emelyanov
[not found] ` <51965707.5010305-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-05-17 16:22 ` Greg KH
2013-05-17 16:10 ` Pavel Emelyanov
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=1368742323-46949-1-git-send-email-snorcht@gmail.com \
--to=snorcht-re5jqeeqqe8avxtiumwx3w@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=tglx-hfZtesqFncYOwBW4kG4KsQ@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).