linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Andrey Vagin <avagin@openvz.org>,
	Pavel Emelyanov <xemul@parallels.com>,
	Vladimir Davydov <vdavydov@parallels.com>
Subject: Re: [patch 0/4] timerfd c/r support, v4
Date: Mon, 30 Jun 2014 23:43:54 +0400	[thread overview]
Message-ID: <20140630194354.GB2305@moon> (raw)
In-Reply-To: <20140623185431.396309193@openvz.org>

On Mon, Jun 23, 2014 at 10:54:31PM +0400, Cyrill Gorcunov wrote:
>
> Hi guys, here is an updated version of c/r support for timerfd files. The main change
> is in how @ticks are restored in patch 3 -- I switched to ioctl code, which is wrapped
> with CONFIG because I still think that while there is only one ioctl designated
> solely for c/r needs no need to build it all the time until explicitly requested.
> Please take a look once time permit. Comments are highly appreciated.
> Also note the last patch is for man-page git repo, not for kernel.

Gentlemen, could you please point me if there something preventing the
series from being picked up? Or there some way to improve the series?

  parent reply	other threads:[~2014-06-30 19:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 18:54 [patch 0/4] timerfd c/r support, v4 Cyrill Gorcunov
2014-06-23 18:54 ` [patch 1/4] timerfd: Implement show_fdinfo method Cyrill Gorcunov
     [not found]   ` <20140623190345.354980826-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-24 22:02     ` Cyrill Gorcunov
2014-06-23 18:54 ` [patch 2/4] docs: procfs -- Document timerfd output Cyrill Gorcunov
2014-06-23 18:54 ` [patch 3/4] timerfd: Implement timerfd_ioctl method to restore timerfd_ctx::ticks Cyrill Gorcunov
     [not found]   ` <20140623190345.499956567-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-24 22:03     ` Cyrill Gorcunov
2014-07-02 16:49       ` Christopher Covington
     [not found]         ` <53B4382F.9030908-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-02 17:04           ` Cyrill Gorcunov
2014-07-02 19:01             ` Arnd Bergmann
2014-07-02 19:07               ` Cyrill Gorcunov
2014-07-02 19:36               ` Cyrill Gorcunov
2014-06-23 18:54 ` [patch 4/4] timerfd.2: Add ioctl method description Cyrill Gorcunov
     [not found] ` <20140623185431.396309193-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-23 19:44   ` [patch 0/4] timerfd c/r support, v4 Andrew Vagin
2014-06-30 19:43 ` Cyrill Gorcunov [this message]
2014-07-15 13:54   ` Cyrill Gorcunov
2014-07-15 16:11     ` Thomas Gleixner
2014-07-15 16:25       ` Cyrill Gorcunov
2014-07-15 21:08         ` Thomas Gleixner
2014-07-15 21:14           ` Cyrill Gorcunov
2014-07-15 21:16             ` Thomas Gleixner
2014-07-15 21:18               ` Cyrill Gorcunov
2014-07-15 21:20                 ` Thomas Gleixner

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=20140630194354.GB2305@moon \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=vdavydov@parallels.com \
    --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).