public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: kernel@kyup.com
Cc: jack@suse.cz, akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsnotify: Remove obsolete documentation
Date: Mon, 1 Jun 2015 18:09:50 +0200	[thread overview]
Message-ID: <20150601160950.GA11971@quack.suse.cz> (raw)
In-Reply-To: <1433164240-10504-1-git-send-email-kernel@kyup.com>

On Mon 01-06-15 16:10:40, kernel@kyup.com wrote:
> From: Nikolay Borisov <kernel@kyup.com>
> 
> should_send_event is no longer part of struct fsnotify_ops
> so remove it
> 
> Signed-off-by: Nikolay Borisov <kernel@kyup.com>
  Right. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  include/linux/fsnotify_backend.h |    2 --
>  1 files changed, 0 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h
> index 0f313f9..65a517d 100644
> --- a/include/linux/fsnotify_backend.h
> +++ b/include/linux/fsnotify_backend.h
> @@ -84,8 +84,6 @@ struct fsnotify_fname;
>   * Each group much define these ops.  The fsnotify infrastructure will call
>   * these operations for each relevant group.
>   *
> - * should_send_event - given a group, inode, and mask this function determines
> - *		if the group is interested in this event.
>   * handle_event - main call for a group to handle an fs event
>   * free_group_priv - called when a group refcnt hits 0 to clean up the private union
>   * freeing_mark - called when a mark is being destroyed for some reason.  The group
> -- 
> 1.7.1
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2015-06-01 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 13:10 [PATCH] fsnotify: Remove obsolete documentation kernel
2015-06-01 16:09 ` Jan Kara [this message]

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=20150601160950.GA11971@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=kernel@kyup.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox