linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov@parallels.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <shawn@churchofgit.com>,
	<tglx@linutronix.de>, <akpm@linux-foundation.org>,
	<avagin@openvz.org>, <xemul@parallels.com>
Subject: Re: [patch 2/3] docs: procfs -- Document timerfd output, v2
Date: Tue, 8 Apr 2014 11:52:14 +0400	[thread overview]
Message-ID: <5343AAAE.9090003@parallels.com> (raw)
In-Reply-To: <20140408074349.GF23983@moon>

On 04/08/2014 11:43 AM, Cyrill Gorcunov wrote:
> CC: Shawn Landden <shawn@churchofgit.com>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: Andrey Vagin <avagin@openvz.org>
> CC: Pavel Emelyanov <xemul@parallels.com>
> CC: Vladimir Davydov <vdavydov@parallels.com>
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> ---
>
> Vladimir, would the below text be more clear?

It looks good to me.

Thanks.

>
>  Documentation/filesystems/proc.txt |   17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>
> Index: linux-2.6.git/Documentation/filesystems/proc.txt
> ===================================================================
> --- linux-2.6.git.orig/Documentation/filesystems/proc.txt
> +++ linux-2.6.git/Documentation/filesystems/proc.txt
> @@ -1741,6 +1741,23 @@ pair provide additional information part
>  	While the first three lines are mandatory and always printed, the rest is
>  	optional and may be omitted if no marks created yet.
>  
> +	Timerfd files
> +	~~~~~~~~~~~~~
> +
> +	pos:	0
> +	flags:	02
> +	mnt_id:	9
> +	clockid: 0
> +	ticks: 0
> +	settime flags: 01
> +	it_value: (0, 49406829)
> +	it_interval: (1, 0)
> +
> +	where 'clockid' is the clock type and 'ticks' is the number of the timer expirations
> +	that have occurred [see timerfd_create(2) for details]. 'settime flags' are
> +	flags in octal form used to setup the timer [see timerfd_settime(2) for
> +	details]. 'it_value' is remaining time until the timer exiration.
> +	'it_interval' is the interval for the timer.
>  
>  ------------------------------------------------------------------------------
>  Configuring procfs


  reply	other threads:[~2014-04-08  7:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 17:47 [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2 Cyrill Gorcunov
2014-04-07 17:47 ` [patch 1/3] timerfd: Implement show_fdinfo method Cyrill Gorcunov
2014-04-08  6:17   ` Vladimir Davydov
2014-04-08  6:42     ` Cyrill Gorcunov
2014-04-08  6:54       ` Vladimir Davydov
2014-04-08  7:10         ` Cyrill Gorcunov
2014-04-07 17:47 ` [patch 2/3] docs: procfs -- Document timerfd output Cyrill Gorcunov
2014-04-08  7:43   ` [patch 2/3] docs: procfs -- Document timerfd output, v2 Cyrill Gorcunov
2014-04-08  7:52     ` Vladimir Davydov [this message]
2014-04-07 17:47 ` [patch 3/3] timerfd: Implement write method Cyrill Gorcunov
2014-04-28 20:53 ` [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2 Cyrill Gorcunov
2014-04-28 20:59   ` Thomas Gleixner
2014-04-28 21:03     ` Cyrill Gorcunov

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=5343AAAE.9090003@parallels.com \
    --to=vdavydov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn@churchofgit.com \
    --cc=tglx@linutronix.de \
    --cc=xemul@parallels.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).