mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Patrick Puzik <p.puzik91@gmail.com>
Cc: Jan Kara <jack@suse.com>, Josef Bacik <jbacik@fb.com>,
	Dave Chinner <dchinner@redhat.com>,
	Nikolay Borisov <kernel@kyup.com>,
	linux-kernel@vger.kernel.org, Patrick Puzik <p.puzi91@gmail.com>
Subject: Re: [PATCH] Add FS_CLOSE_READ and FS_CLOSE_NOREAD flag to fsnotify
Date: Mon, 21 Sep 2015 14:37:22 -0700	[thread overview]
Message-ID: <20150921143722.2f404ed9e66233a3d38a7d46@linux-foundation.org> (raw)
In-Reply-To: <1442783255-7457-1-git-send-email-p.puzi91@gmail.com>

On Sun, 20 Sep 2015 23:07:35 +0200 Patrick Puzik <p.puzik91@gmail.com> wrote:

> Attached is a patch which is a preparation for the later support of an event notification,
> when an unreadable or readable file was closed.

People will want to see the whole patchset.

> --- a/include/linux/fsnotify_backend.h
> +++ b/include/linux/fsnotify_backend.h
> @@ -28,6 +28,8 @@
>  #define FS_ATTRIB		0x00000004	/* Metadata changed */
>  #define FS_CLOSE_WRITE		0x00000008	/* Writtable file was closed */
>  #define FS_CLOSE_NOWRITE	0x00000010	/* Unwrittable file closed */
> +#define FS_CLOSE_READ           0x00000011      /* Unreadable file closed */
> +#define FS_CLOSE_NOREAD         0x00000012      /* Readable file was closed */

The comments appear to be reversed.



  reply	other threads:[~2015-09-21 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 21:07 Patrick Puzik
2015-09-21 21:37 ` Andrew Morton [this message]
2015-09-22  9:06 ` Jan Kara
2015-09-23 18:32   ` Patrick Puzik
2015-09-24  8:00     ` 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=20150921143722.2f404ed9e66233a3d38a7d46@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dchinner@redhat.com \
    --cc=jack@suse.com \
    --cc=jbacik@fb.com \
    --cc=kernel@kyup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.puzi91@gmail.com \
    --cc=p.puzik91@gmail.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

all inboxes | Powered by JetHome®