From: Cyrill Gorcunov <gorcunov@virtuozzo.com>
To: Jan Kara <jack@suse.cz>
Cc: Kirill Tkhai <ktkhai@virtuozzo.com>,
akpm@linux-foundation.org, amir73il@gmail.com,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] inotify: Extend ioctl to allow to request id of new watch descriptor
Date: Thu, 8 Feb 2018 20:58:33 +0300 [thread overview]
Message-ID: <20180208175833.GC17303@uranus.lan> (raw)
In-Reply-To: <20180208161400.t4i42kkpddm2k766@quack2.suse.cz>
On Thu, Feb 08, 2018 at 05:14:00PM +0100, Jan Kara wrote:
> >
> > Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
>
> I'm not thrilled by this but OTOH I also don't know about a better option.
> The patch as such looks OK to me so unless someone objects I'll take it to
> my tree in a few days.
Reviewed-by: Cyrill Gorcunov <gorcunov@openvz.org>
next prev parent reply other threads:[~2018-02-08 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:07 [PATCH] inotify: Extend ioctl to allow to request id of new watch descriptor Kirill Tkhai
2018-02-08 16:02 ` Matthew Wilcox
2018-02-09 8:26 ` Kirill Tkhai
2018-02-09 13:28 ` Matthew Wilcox
2018-02-09 15:05 ` Kirill Tkhai
[not found] ` <151810242614.30935.12876744458891870220.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2018-02-08 16:14 ` Jan Kara
2018-02-08 16:14 ` Jan Kara
2018-02-08 17:58 ` Cyrill Gorcunov [this message]
2018-02-09 15:04 ` [PATCH v2] " Kirill Tkhai
2018-02-09 15:04 ` Kirill Tkhai
2018-02-09 15:14 ` Matthew Wilcox
2018-02-09 20:56 ` Andrew Morton
2018-02-09 22:45 ` Kirill Tkhai
2018-02-11 11:30 ` Stef Bon
[not found] ` <CANXojcxKH1zFHOPsJh7zbjshUkFGagah-vN6EvMU7Q-9kLFmpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-12 8:42 ` Kirill Tkhai
2018-02-12 8:42 ` Kirill Tkhai
[not found] ` <bb9bafab-9a50-d19e-7293-65e74aca4720-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2018-02-14 10:18 ` Jan Kara
2018-02-14 10:18 ` Jan Kara
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=20180208175833.GC17303@uranus.lan \
--to=gorcunov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=ktkhai@virtuozzo.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.