From: Ian Kent <raven@themaw.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 5/6] autofs: remove unused ino field inode
Date: Fri, 17 Jun 2022 13:35:51 +0800 [thread overview]
Message-ID: <165544415191.250070.12106625168524302864.stgit@donald.themaw.net> (raw)
In-Reply-To: <165544393032.250070.3426550720222448062.stgit@donald.themaw.net>
Remove the unused inode field of the autofs dentry info
structure.
Signed-off-by: Ian Kent <raven@themaw.net>
---
fs/autofs/autofs_i.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/autofs/autofs_i.h b/fs/autofs/autofs_i.h
index 0117d6e06300..d5a44fa88acf 100644
--- a/fs/autofs/autofs_i.h
+++ b/fs/autofs/autofs_i.h
@@ -51,8 +51,6 @@ extern struct file_system_type autofs_fs_type;
*/
struct autofs_info {
struct dentry *dentry;
- struct inode *inode;
-
int flags;
struct completion expire_complete;
next prev parent reply other threads:[~2022-06-17 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:35 [PATCH 0/6] autofs: misc patches Ian Kent
2022-06-17 5:35 ` [PATCH 1/6] autofs: use inode permission method for write access Ian Kent
2022-06-17 5:35 ` [PATCH 2/6] autofs: make dentry info count consistent Ian Kent
2022-06-17 5:35 ` [PATCH 3/6] autofs: use dentry info count instead of simple_empty() Ian Kent
2022-06-17 5:35 ` [PATCH 4/6] autofs: add comment about autofs_mountpoint_changed() Ian Kent
2022-06-17 5:35 ` Ian Kent [this message]
2022-06-17 5:35 ` [PATCH 6/6] autofs: manage dentry info mount trigger flags better Ian Kent
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=165544415191.250070.12106625168524302864.stgit@donald.themaw.net \
--to=raven@themaw.net \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
/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.