From: Jan Kara <jack@suse.cz>
To: YueHaibing <yuehaibing@huawei.com>
Cc: jack@suse.cz, amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fanotify: Remove unused extern declaration fsnotify_get_conn_fsid()
Date: Tue, 1 Aug 2023 23:46:40 +0200 [thread overview]
Message-ID: <20230801214640.3hgms34jme6357cg@quack3> (raw)
In-Reply-To: <20230725135528.25996-1-yuehaibing@huawei.com>
On Tue 25-07-23 21:55:28, YueHaibing wrote:
> This is never used, so can remove it.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Thanks! I've added the patch to my tree.
Honza
> ---
> include/linux/fsnotify_backend.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h
> index d7d96c806bff..c0892d75ce33 100644
> --- a/include/linux/fsnotify_backend.h
> +++ b/include/linux/fsnotify_backend.h
> @@ -760,9 +760,6 @@ extern void fsnotify_init_mark(struct fsnotify_mark *mark,
> /* Find mark belonging to given group in the list of marks */
> extern struct fsnotify_mark *fsnotify_find_mark(fsnotify_connp_t *connp,
> struct fsnotify_group *group);
> -/* Get cached fsid of filesystem containing object */
> -extern int fsnotify_get_conn_fsid(const struct fsnotify_mark_connector *conn,
> - __kernel_fsid_t *fsid);
> /* attach the mark to the object */
> extern int fsnotify_add_mark(struct fsnotify_mark *mark,
> fsnotify_connp_t *connp, unsigned int obj_type,
> --
> 2.34.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-08-01 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 13:55 [PATCH -next] fanotify: Remove unused extern declaration fsnotify_get_conn_fsid() YueHaibing
2023-08-01 21:46 ` 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=20230801214640.3hgms34jme6357cg@quack3 \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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).